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/SummerSec/SumSec-SkillsWrote 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/summersec/sumsec-skills/revise-claude-md)<a href="https://agentmods.dev/commands/summersec/sumsec-skills/revise-claude-md"><img src="https://agentmods.dev/badge/commands/summersec/sumsec-skills/revise-claude-md/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/summersec/sumsec-skills/revise-claude-md"><img src="https://agentmods.dev/badge/commands/summersec/sumsec-skills/revise-claude-md.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.00345 |
| Opus 5 | $0.00005 | $0.00172 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
revise-claude-md 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 10d 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.
This is a copy
100% identical to revise-claude-md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Review this session for learnings about working with Claude Code in this codebase. Update CLAUDE.md with context that would help future Claude sessions be more effective.
Step 1: Reflect
What context was missing that would have helped Claude work more effectively?
- Bash commands that were used or discovered
- Code style patterns followed
- Testing approaches that worked
- Environment/configuration quirks
- Warnings or gotchas encountered
Step 2: Find CLAUDE.md Files
find . -name "CLAUDE.md" -o -name ".claude.local.md" 2>/dev/null | head -20
Decide where each addition belongs:
CLAUDE.md- Team-shared (checked into git).claude.local.md- Personal/local only (gitignored)
Step 3: Draft Additions
Keep it concise - one line per concept. CLAUDE.md is part of the prompt, so brevity matters.
Format: <command or pattern> - <brief description>
Avoid:
- Verbose explanations
- Obvious information
- One-off fixes unlikely to recur
Step 4: Show Proposed Changes
For each addition:
### Update: ./CLAUDE.md
**Why:** [one-line reason]
\`\`\`diff
+ [the addition - keep it brief]
\`\`\`
Step 5: Apply with Approval
Ask if the user wants to apply the changes. Only edit files they approve.
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.
- 10d ago First seen · 55 lines · 11 tokens per session scan A d59ffd7ef2b7
revise-claude-md is a command published in the GitHub repository SummerSec/SumSec-Skills (8 stars, last pushed 26d ago), licensed Apache-2.0. It adds 11 tokens to every session and 345 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to revise-claude-md, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
riskreview
The user invoked the /riskreview facade command from the risk-review-pipeline pack.
hello-stranger
Say hello stranger.
approval
The user invoked the /approval facade command from the approval-node-pipeline pack.
aw
The user invoked the /approval-web facade command from the approval-node-pipeline pack.
kf
A customer-support command for TeamClaw, a software product. It sends a user's question to a support workflow that can search help information, examine logs, and create defect reports.
workflow-dispatcher
The user invoked the /workflow-dispatcher facade command from the workflow-dispatcher pack.