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 gmickel/flow-next --skill flow-next-tracker-syncgit 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/skills/gmickel/flow-next/flow-next-tracker-sync)<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-tracker-sync"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-tracker-sync/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/gmickel/flow-next/flow-next-tracker-sync"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-tracker-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01510 |
| Opus 5.5 | $0.00018 | $0.00604 |
| Sonnet 5.5 | $0.00009 | $0.00302 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
flow-next-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 16d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
flow-next-tracker-sync
The flow spec is the source of truth and quality layer. The tracker is a co-editable projection. Tracker activity never starts agents or changes Flow task state.
Read working-rules.md first unless you already have this run; it holds for every step of this skill.
Load the reached path
Read steps.md for the operation sequence and references/adapter-interface.md for the normalized contract. Load only references needed by the reached path:
- Body comparison or conflict: references/body-merge.md.
- Status projection: references/status-sync.md.
- Comment or question-valve content: references/comments-sync.md.
- Hybrid identifiers: references/identity.md.
- Linear transport shape: references/linear-ladder.md, then only the reached MCP or GraphQL reference.
- GitHub, GitLab, or Jira transport shape: the matching provider reference only.
Never load an unselected provider merely because another reference links it.
Deterministic boundary
flowctl tracker owns tracker transport, normalization, credentials, retries,
capability degradation, lifecycle ordering, receipts, and atomic local state.
The skill supplies only approved semantic inputs and reacts to the structured
result. Do not reconstruct provider requests in skill prose or shell.
Use the lifecycle facade for event-driven projection:
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"
$FLOWCTL tracker sync "$SPEC_ID" --op "$OP" --event "$EVENT" \
--flow-file "$FLOW_FILE" --body-file "$BODY_FILE" \
--comments-file "$COMMENTS_FILE" --source-body-file "$SOURCE_BODY_FILE"
What ships with it
16 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.
- agents/openai.yaml 233 B
- references/adapter-interface.md 5.3 KB
- references/backlog-ops.md 2.7 KB
- references/body-merge.md 19 KB
- references/chart-subjects.md 3.9 KB
- references/comments-sync.md 20 KB
- references/create-first.md 1.9 KB
- references/github.md 1.9 KB
- references/gitlab.md 1.6 KB
- references/identity.md 6.8 KB
- references/jira.md 4.1 KB
- references/linear-graphql.md 1.5 KB
- references/linear-ladder.md 1.6 KB
- references/linear-mcp.md 1.0 KB
- references/status-sync.md 28 KB
- steps.md 11 KB
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.
- 16d ago Changed · -5 lines c4422f7ccc29
- 18d ago Changed · +2 lines cd9141b126f2
- 23d ago Changed · +2 lines e5a4c67af860
- 1mo ago First seen · 133 lines · 44 tokens per session scan A 771ec83a860b
flow-next-tracker-sync is a skill published in the GitHub repository gmickel/flow-next (711 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,510 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
st-setup-project
Smalltalk (Pharo/Squeak) project boilerplate creator. Use when the user asks to create a new Pharo/Smalltalk project from scratch, when project structure is missing (no src/ directory or .project file), when the user wants to start a new Smalltalk development project, or when setting up BaselineOf, Core, and Tests…
kanban
Use when a prompt contains a new bug/feature/change not yet tracked, or when an item's status changes — capture and maintain it in the project's beads tracker (Inbox→Backlog with Definition of Ready, priorities, the pipe-separated note format).
project-discuss
A project-discussion management workflow that keeps track of decisions, open questions, project context, and incidents. It uses a project's cadence files, which are shared records for ongoing discussions and decisions.
subtask-update
Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.