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 skills/bengous/claude-code-plugins/revise-claude-mdnpx skills add bengous/claude-code-plugins --skill revise-claude-mdgit clone --depth 1 https://github.com/bengous/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/skills/bengous/claude-code-plugins/revise-claude-md)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/revise-claude-md"><img src="https://agentmods.dev/badge/skills/bengous/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.00033 | $0.00551 |
| Opus 5 | $0.00016 | $0.00275 |
| Sonnet 5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
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 5d 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.
What it actually says
Review this session for learnings about working with Claude Code in this codebase. Update project memory with context that would help future Claude sessions be more effective.
Scope boundary: this skill captures current-session learnings. Syncing CLAUDE.md against git history and codebase evolution is /sync-claude-md's job.
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 Memory Files
Use Glob: **/CLAUDE.md, .claude/CLAUDE.md, .claude/rules/**/*.md, CLAUDE.local.md. Also check discovered files for @path imports pointing to other memory files.
Decide where each addition belongs:
CLAUDE.md- Team-shared, always-on (checked into git); nested ones scope to their directory.claude/rules/<topic>.md- Team-shared thematic rules; an existing rules file covering the topic wins over CLAUDE.md, and prefer a new one over growing an already-long CLAUDE.md- Personal/local only - gitignored
CLAUDE.local.md(loads alongside CLAUDE.md; append to it if present); for prefs shared across worktrees, a home-dir file imported via@~/.... Note:@pathimports are composition, not privacy: a versioned import target is team-visible.
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: [target file]
**Why:** [one-line reason]
\`\`\`diff
+ [the addition - keep it brief]
\`\`\`
Step 5: Apply with Approval
Ask if the user wants to apply the changes. Do not call Edit or Write before approval; only touch 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.
- 5d ago First seen · 62 lines · 33 tokens per session scan A 7e7331f36648
revise-claude-md is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 551 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-31.
Other skills, from other repositories
self-awareness
Claude Science's own session database schema and SDK surface for introspection via host.query(). Load this when you need to query your own conversation history, token usage, cost accounting, execution log, or artifact metadata beyond what host.frames()/host.artifacts() provide — e.g. "how many tokens has this session…
ima-note
IMA 个人笔记服务 API skill，用于管理用户的 IMA 笔记。支持搜索笔记、浏览笔记本、获取笔记内容、新建笔记和追加内容。 当用户提到笔记、备忘录、记事、知识库，或者想要查找、阅读、创建、编辑笔记内容时，使用此 skill。 即使用户没有明确说"笔记"，只要意图涉及个人文档的存取（如"帮我记一下"、"我之前写过一个关于XX的东西"、"把这段内容保存下来"），也应触发此 skill。.
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what…
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when (1) a command, tool, API, or operation fails; (2) the user corrects you or rejects your work; (3) you realize your knowledge is outdated or incorrect; (4) you…
credential-recipe-research
Lookup procedure for Simplified Custom Auth recipe fields — sources the auth template, the key-issuing docsUrl and an auth-rejecting testUrl from the provider's real documentation instead of memory. Load before composing credentialHints for a service without a dedicated credential type (the post-build-flow setup…
flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.