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/shenchangmin/cairnkitWrote 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/shenchangmin/cairnkit/flow-status)<a href="https://agentmods.dev/commands/shenchangmin/cairnkit/flow-status"><img src="https://agentmods.dev/badge/commands/shenchangmin/cairnkit/flow-status/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/commands/shenchangmin/cairnkit/flow-status"><img src="https://agentmods.dev/badge/commands/shenchangmin/cairnkit/flow-status.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.00020 | $0.00301 |
| Opus 5.5 | $0.00008 | $0.00120 |
| Sonnet 5.5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
flow-status 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 1mo 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
/flow-status
Report where the current run stands. This is read-only.
Steps
- Run
cairn --root . config show.- Exit
2→ nocairnkit.yaml; suggest theteam-initentrypoint and stop. - Exit
0→ ifhas_runis false, report "no run yet" and suggest theflow-runentrypoint.
- Exit
- Run
cairn --root . state show.- Exit
4→ STATE corrupt; show the repair guidance from stderr verbatim and stop. - Exit
0→ parse the JSON, then runcairn --root . state resumefor thepausedflag.
- Exit
- Present a concise human summary:
- Stage and whether the run is paused (awaiting a CLARIFY approval — name what).
- History (stages completed so far).
- Artifacts produced (paths under
docs/workflows/<run-id>/). - Next action: if paused → resume through the
flow-runentrypoint after review. If the stage isDONE, say the run is complete and suggest using that entrypoint to start a new run. Otherwise use it to continue the active run.
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.
- 1mo ago First seen · 25 lines · 20 tokens per session scan A eb71b78cbe55
flow-status is a command published in the GitHub repository shenchangmin/cairnkit (1 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 301 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checkpoint
Write a project checkpoint to this project's AgentDB store with ruflo memory store — the goal, the acceptance contract, the decisions, what is done, what is blocked, and the exact next action — and prove it by exact-key ruflo memory retrieve. The next session (Claude Code or Codex) restores the newest checkpoint by…
pm-autoplan
Orchestre les trois angles de revue (stratégie, utilisateur, faisabilité) en parallèle, puis synthétise leurs pages de stress-test dans output/.
pm-epic-01-happy
Un PRD complet est disponible dans output/ : il contient des exigences P0/P1 avec des critères d'acceptation et une section ## Métriques de succès. Le pm-decomposer crée un epic avec ## Success Criteria et des issues enfants P0/P1 avec critères d'acceptation. Les issues sont liées à l'epic.
pm-review-user-01-happy
Un PRD est disponible dans output/. Le wiki contient des pages persona- et interview- avec des verbatims. Le pm-user-advocate vérifie l'alignement du PRD avec les personas, identifie les personas non servis, cite les verbatims contradictoires, et évalue le niveau de confiance de chaque claim. Une page type…
pm-review-feasibility
Stress-teste un brouillon (PRD, roadmap ou autre output/) sous l'angle faisabilité technique — claims de complexité, dépendances, risques d'intégration et décisions d'architecture antérieures. Triggers — est-ce techniquement faisable, auditer la faisabilité, vérifier la cohérence avec l'archi.
pm-review-strategy
Stress-teste un brouillon (PRD, roadmap ou autre output/) sous l'angle stratégie/périmètre et dépose un stress-test dans wiki/. Triggers — attaquer un PRD sous l'angle stratégie, challenger la roadmap, vérifier que ça reste dans le périmètre.