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 agentmods add commands/dgouron/review-flow/statusgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/status)<a href="https://agentmods.dev/commands/dgouron/review-flow/status"><img src="https://agentmods.dev/badge/commands/dgouron/review-flow/status.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 | $0.00000 | $0.00349 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
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 4d 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
/status — Complete Project Diagnostic
Read-only. No modifications.
1. Technical Health
Run and report results:
yarn typecheck # TypeScript validation
yarn lint # Biome linting
yarn test:ci # Tests
yarn coverage # Coverage report
2. Structure by Module
For each directory under src/:
- File count
- Test count (matching files in
src/tests/units/)
3. Technical Debt
- Files > 200 lines (list with line count)
TODO/FIXME/HACK/WORKAROUNDgrep (count + locations)
4. Git
- Current branch
- Last 10 commits (
git log --oneline -10) - Uncommitted files (
git status)
5. Outdated Dependencies
yarn outdated
6. .claude/ Coherence
- Structure files present (rules/, roles/, agents/, skills/, commands/)
- Agents → Roles mapping verified (each agent references a valid role)
7. Synthesis
| Check | Status |
|---|---|
| Types | PASS / FAIL |
| Lint | PASS / FAIL |
| Tests | PASS / FAIL |
| Coverage | X% statements, X% branches |
Debt metrics: Files > 200 lines, TODO count, outdated deps
Problems list or "All good"
Rules
- Read-only — do not modify anything
- If a command fails, note the error and continue
- Report facts, not interpretation
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.
- 4d ago First seen · 62 lines · 0 tokens per session scan A 285d73d0d96a
status is a command published in the GitHub repository DGouron/review-flow (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 349 tokens. 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 commands, from other repositories
autobot
Launch a bot command in an isolated autobot session with its own worktree, backend, and frontend.
brooks-audit
Run a Brooks-Lint architecture audit.
brooks-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
fixbot
You are the orchestrator for the fixbot workflow. Fixbot fixes a Linear issue, running directly in this project against the locally running server. For an isolated worktree version, use /autobot /fixbot instead.
qabot-report
Regenerate the QA report from existing review files.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.