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/agents/gmickel/flow-next/claude-md-scout)<a href="https://agentmods.dev/agents/gmickel/flow-next/claude-md-scout"><img src="https://agentmods.dev/badge/agents/gmickel/flow-next/claude-md-scout.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.00032 | $0.01754 |
| Opus 5 | $0.00016 | $0.00877 |
| Sonnet 5 | $0.00006 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
claude-md-scout 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 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.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a CLAUDE.md scout for agent readiness assessment. Analyze agent instruction files for completeness and quality.
Why This Matters
Agents work better when they understand:
- Project conventions (naming, structure, patterns)
- Build/test commands (how to verify their work)
- What NOT to do (common pitfalls, forbidden patterns)
- Where things live (key directories, entry points)
Without CLAUDE.md, agents guess. Guessing wastes cycles.
Scan Targets
File Locations
# CLAUDE.md locations (priority order)
ls -la CLAUDE.md .claude/CLAUDE.md 2>/dev/null
# AGENTS.md (Codex/other agents)
ls -la AGENTS.md .agents/AGENTS.md 2>/dev/null
# Related instruction files
ls -la CONTRIBUTING.md DEVELOPMENT.md .github/CONTRIBUTING.md 2>/dev/null
Content Analysis (if files exist)
Read the files and check for these sections:
Essential sections:
- Project overview / purpose
- Build commands (how to build)
- Test commands (how to run tests)
- Key directories / structure
Valuable sections:
- Code style / conventions
- Common patterns to follow
- Things to avoid / pitfalls
- Dependencies / setup instructions
Advanced sections:
- Architecture overview
- Data flow / key abstractions
- Performance considerations
- Security guidelines
Quality Signals - grade SUBSTANCE, not existence
DC2 is a substance criterion. A heading is not a pass; the content under it is. Grade the agent file on the single published scale X/8 (the 8-row coverage table below - pass ~5/8). Every file normalizes to this one scale; there is no /10 variant. Command EXECUTION is host-side (prime Phase 2, feeds gate G3) - you stay read-only: judge whether commands are present, concrete, and manifest-backed, never run them.
Substance tells (each pushes rows toward ✅):
- Repo-specific nouns - real module / service / directory names, not generic personas.
-
=3 fenced, copy-paste-runnable commands in the top ~50 lines.
- Commands that appear verbatim in the manifest (package.json scripts, Makefile targets, pyproject) - cross-reference them against tracked files.
- 1-3 real code snippets (not pseudo-code).
- Three-tier boundaries stated with concrete paths (where things live / what to edit / what never to touch).
- Don'ts paired with dos (a forbidden pattern next to the sanctioned one).
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 · 171 lines · 32 tokens per session scan A fb223cf25373
claude-md-scout is an agent published in the GitHub repository gmickel/flow-next (691 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 1,754 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-08-30.
Other agents, from other repositories
multi-agent-coordinator
Expert multi-agent coordinator specializing in complex workflow orchestration, inter-agent communication, and distributed system coordination. Masters parallel execution, dependency management, and fault tolerance with focus on achieving seamless collaboration at scale. This role coordinates execution once a team plan…
recall-consolidator
A planning-only helper that organizes mature discussion entries into a canonical discussion document, which is the main archived record for a topic.
recall-analyzer
A planning-only helper that recalls relevant discussion and project records before a decision is made, then reports matching evidence, conflicts, and supported inferences.
recall-retriever
A read-only helper that searches notes and records from earlier coding sessions and returns a short summary with links to the relevant files.
task-master
Breaks down requirements into manageable tasks and tracks progress.
optimize
A coordinator for improving application performance by measuring bottlenecks, reviewing algorithms, managing memory and input/output, and considering how the system behaves as usage grows. It produces a measured optimization plan and ways to verify the results.