Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add FlowRegSuite/flowreg-agent-skills --skill flowreg-plangit clone --depth 1 https://github.com/FlowRegSuite/flowreg-agent-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/flowregsuite/flowreg-agent-skills/flowreg-plan)<a href="https://agentmods.dev/skills/flowregsuite/flowreg-agent-skills/flowreg-plan"><img src="https://agentmods.dev/badge/skills/flowregsuite/flowreg-agent-skills/flowreg-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/flowregsuite/flowreg-agent-skills/flowreg-plan"><img src="https://agentmods.dev/badge/skills/flowregsuite/flowreg-agent-skills/flowreg-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00090 | $0.02014 |
| Opus 5 | $0.00045 | $0.01007 |
| Sonnet 5 | $0.00018 | $0.00403 |
| Haiku 4.5 | $0.00009 | $0.00201 |
Grade A, and why
flowreg-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowRegSuite planning and routing
1. Purpose
Turn a vague request about "fixing motion" into one explicitly chosen capability, a runtime that is verified to exist, a reference strategy, a small pilot, a resource estimate, and quality-control gates that decide in advance what would count as failure.
This skill produces a plan. It does not run a full registration.
2. Use this skill when
- The user asks to correct, stabilise, register or align microscopy data and the workflow is not already settled.
- Axes, channel meaning, voxel spacing, reference availability or hardware are uncertain.
- More than one recording may need to share coordinates.
- You need to know whether a capability is even available before promising anything.
3. Do not use this skill when
- The workflow is already chosen and a plan exists — go straight to the execution skill.
- A run has finished and needs assessment — use
flowreg-qc-and-audit. - The request is about one-dimensional signals or evoked responses. That is
flowreg1D, which ships no skill in this release; report the capability status instead.
4. Required inputs and metadata
Collect all of the following. Where something is unavailable, record it as an unresolved question rather than guessing.
| Group | Items |
|---|---|
| Data | file format, array shape, named axis order, dtype, value range, frame/volume count, approximate size |
| Semantics | which axis is time, which is z, which is channel, and what each channel is (structural vs functional) |
| Physical | pixel and voxel spacing with units, frame or volume rate |
| Reference | is a reference volume or reference recording available, and how was it acquired |
| Scope | one recording, or several that must share coordinates |
| Resources | free disk, RAM, CPU count, GPU model and memory, whether the runtime can use that GPU |
| Location | local, network mount, or cluster |
Never infer axis meaning from array rank or from which dimension is longest. A 4-D array may be
TZYX, TYXC or ZYXC. Getting this wrong silently registers the wrong thing. Axis order must
come from file metadata, acquisition software, or an explicit statement by the user, and the plan
must record which of those it was.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 167 lines · 90 tokens per session scan A 16bb7064a22b
flowreg-plan is a skill published in the GitHub repository FlowRegSuite/flowreg-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 2,014 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…