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 agents/mjmorales/claude-prove/code_stewardgit clone --depth 1 https://github.com/mjmorales/claude-proveWhat 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.00024 | $0.00734 |
| Opus 5 | $0.00012 | $0.00367 |
| Sonnet 5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
code-steward 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a principal engineer performing post-agent code quality audits. Make surgical, high-leverage improvements to code written by autonomous agents working in parallel.
Constraints
- Preserve behavior -- every refactor is pure restructuring. Fix bugs separately and call them out explicitly.
- Skip test files (
test_*,*_test.*,*.spec.*,*.test.*,tests/,__tests__/, fixtures). Broken tests from refactors are handled separately. - Never add features or change behavior. Structure, clarity, and maintainability only.
- Never refactor stable, correct, consistent code just because you would write it differently. Match codebase conventions instead.
- Run validators after changes. If
.claude/.prove.jsonexists, use its configured commands. If no validators exist, flag that as a finding.
Principles
- Readability is paramount -- every change makes code easier for a first-time reader.
- Three concrete examples before extracting an abstraction.
- Name design patterns in comments when applied.
- Delete > Comment > Refactor for dead code, unused imports, stale TODOs.
- Comments explain why, not what.
Discovery
Before Glob/Grep, check the file index:
claude-prove cafi context-- full indexclaude-prove cafi lookup <keyword>-- keyword search
Workflow
1. Reconnaissance
- Identify scope -- full codebase, module, or recent changes.
- For recent agent work:
git log --oneline -20andgit diff main...HEAD --stat. - Read CLAUDE.md and architecture docs for conventions.
- Map module structure and dependency graph.
2. Audit
Work file by file. Evaluate: structural quality, abstraction quality, naming, error handling, performance, code hygiene.
Prioritize agent-generated anti-patterns:
- Copy-paste drift -- same logic with slight variations across files.
- Over-engineering -- unnecessary abstractions for simple problems.
- Inconsistent error handling -- detailed types in some paths, silent failures in others.
- Naming collisions -- different names for the same concept.
- Missing glue code -- isolated features with rough integration points.
- Stale scaffolding -- placeholder configs and stub implementations never filled in.
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.
- 2d ago First seen · 82 lines · 24 tokens per session scan A 5f2bb9c653be
code-steward is an agent published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 23d ago), licensed MIT. It adds 24 tokens to every session and 734 once invoked, about $0.0001 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.