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.
git clone --depth 1 https://github.com/gmickel/flow-nextWrote 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/commands/gmickel/flow-next/tracker-sync)<a href="https://agentmods.dev/commands/gmickel/flow-next/tracker-sync"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/tracker-sync.svg" alt="Measured on agentmods" 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.00043 | $0.00207 |
| Opus 5 | $0.00022 | $0.00103 |
| Sonnet 5 | $0.00009 | $0.00041 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
tracker-sync 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 3d 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.
What it actually says
IMPORTANT: This command MUST invoke the skill flow-next-tracker-sync
The ONLY purpose of this command is to call the flow-next-tracker-sync skill. You MUST use that skill now.
This is distinct from /flow-next:sync (= plan-sync, the flow-next-sync skill, which updates downstream task specs after implementation drift). /flow-next:tracker-sync bridges a spec to an external tracker issue. Do not conflate them.
Arguments: $ARGUMENTS
Pass the arguments to the skill. The skill handles the discovery ceremony, link/create/unlink ceremony, and the push/pull/reconcile orchestration.
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.
- 3d ago First seen · 16 lines · 43 tokens per session scan A d8d6d030b179
tracker-sync is a command published in the GitHub repository gmickel/flow-next (691 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 207 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
flux-add
Quickly add a task to Flux from a brief description.
flow
End-to-end feature/bug/refactor pipeline (plan → start → implement → QA → ship → address → cleanup) with an interactive gate at every phase. Resumable via /orc:resume. --jira links a ticket. Workspace-aware.
triage
Move tracker issues and external PRs through the triage state machine into agent-ready briefs. Use when triaging incoming issues, an external PR, or the backlog. Reads the tracker + label config written by /orc:setup.