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/pleaseai/claude-code-plugins/revise-claude-mdgit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote 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/pleaseai/claude-code-plugins/revise-claude-md)<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/revise-claude-md"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/revise-claude-md.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.00011 | $0.00576 |
| Opus 5 | $0.00005 | $0.00288 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade B, and why
revise-claude-md 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 3d 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.
find ./.claude/rules -name "*.md" 2>/dev/null This is a copy
86% identical to revise-claude-md — 41 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 and Project Rules
# CLAUDE.md files
find . \( -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" \) 2>/dev/null | head -20
# Project rules
find ./.claude/rules -name "*.md" 2>/dev/null
Decide where each addition belongs:
CLAUDE.md- Team-shared (checked into git).claude.local.md- Personal/local only (gitignored).claude/rules/*.md- Modular, topic-specific rules (path-based loading)
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>
CLAUDE.md vs Rules decision:
- CLAUDE.md: Global instructions (applies to entire project)
- .claude/rules/*.md: Path-specific instructions (use
paths:frontmatter)
Rules Frontmatter example:
---
paths: src/api/**/*.ts,src/services/**/*.ts
---
Note:
paths:uses comma-separated format (not YAML array)
Avoid:
- Verbose explanations
- Obvious information
- One-off fixes unlikely to recur
- Content that duplicates existing rules
Step 4: Show Proposed Changes
For each addition:
### Update: ./CLAUDE.md
**Why:** [one-line reason]
\`\`\`diff
+ [the addition - keep it brief]
\`\`\`
For new rules file:
### Create: ./.claude/rules/api-patterns.md
**Why:** API development patterns apply only to specific paths
\`\`\`yaml
---
paths: src/api/**/*.ts
---
# API Development Rules
- Use dependency injection pattern
- All endpoints must have OpenAPI docs
\`\`\`
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.
- 3d ago First seen · 92 lines · 11 tokens per session scan B b56a3b374027
revise-claude-md is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 576 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 86% identical to revise-claude-md, differing in 41 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.