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/timgranlundmarsden/claude-agent-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/timgranlundmarsden/claude-agent-flow/diagnostic)<a href="https://agentmods.dev/commands/timgranlundmarsden/claude-agent-flow/diagnostic"><img src="https://agentmods.dev/badge/commands/timgranlundmarsden/claude-agent-flow/diagnostic/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/timgranlundmarsden/claude-agent-flow/diagnostic"><img src="https://agentmods.dev/badge/commands/timgranlundmarsden/claude-agent-flow/diagnostic.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.00011 | $0.02129 |
| Opus 5 | $0.00005 | $0.01064 |
| Sonnet 5 | $0.00002 | $0.00426 |
| Haiku 4.5 | $0.00001 | $0.00213 |
Grade B, and why
diagnostic scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. **Settings-derived plugin cache**: Read `.claude/settings.json`, find any `enabledPlugins` key containing "agent-flow". Extract the plugin key. Check `~/.claude/plugins/cache/<plugin-key>/agent-flow/.claude-agent-flow The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 174 lines · 11 tokens per session scan B 55f698264f94
diagnostic is a command published in the GitHub repository timgranlundmarsden/claude-agent-flow (2 stars, last pushed 3mo ago), with no licence file. It adds 11 tokens to every session and 2,129 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
fix-develop
Autonomous fix loop for failing CI on the repo's default branch.
detectar-ambiguedad
Detectar ambigüedades y contradicciones en specs de forma exhaustiva.
diagnostico
Verificar la salud del setup de Don Cheli en el proyecto actual.