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/sync-claude-mdnpx skills add bengous/claude-code-plugins --skill sync-claude-mdgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWhat 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.00030 | $0.00630 |
| Opus 5 | $0.00015 | $0.00315 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
sync-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 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync CLAUDE.md
Keeps project-level CLAUDE.md synchronized with codebase evolution. Never commits: the user commits manually.
Preconditions:
- Not in a git repo (
git rev-parse --is-inside-work-treefails) → the analysis below is git history; without it this skill has nothing to work from. Point the user to/initand stop. - Locate the file: check
./CLAUDE.md(preferred), then./.claude/CLAUDE.md. If both exist, warn about the duplicate, recommend consolidating to./CLAUDE.md, and ask which to update. Missing → suggest/initto bootstrap one and stop.
1. Gather change context
Use the path located above (not a hardcoded CLAUDE.md):
path=<located path, e.g. ./CLAUDE.md>
last=$(git log --follow --format="%H" -1 -- "$path")
git rev-list --count "$last"..HEAD
git log --oneline "$last"..HEAD
Identify commits that contradict or outgrow what CLAUDE.md claims: library migrations, new tools or commands, architecture shifts. If more than 10 commits, delegate complex change areas to a subagent via the Agent tool; require its findings in the format <sha> | <CLAUDE.md claim impacted>, one line each, so the SHAs survive into the proposal. For 10 or fewer, read the commits directly (git show --stat on key ones).
Zero relevant commits since the last CLAUDE.md change → say so and stop. Do not pad an empty proposal.
2. Proposal
Draft a proposal: summary, then sections to add / modify / remove, each with exact content, a one-line rationale, and a Motivated by: <sha> (or <A>..<B>) line. Every SHA cited in a Motivated by: line (for a range, both endpoints) must appear in step 1's git log output. An item without a motivating commit is not proposed. General improvement of the file is context-audit's territory, not this skill's. Preserve existing good content; never remove anything whose purpose you don't understand.
3. Approval and apply
Present the full proposal, then use AskUserQuestion to confirm (apply / reject). On approval: apply with Edit (Write only for a full rewrite), summarize what changed, remind the user to review and commit. On rejection: offer to save the proposal to a file for later.
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 · 48 lines · 30 tokens per session scan A 9feadab0aa04
sync-claude-md is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 630 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
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
devops
DevOps 能力索引。Git、测试、DevSecOps、数据库。当用户提到 DevOps、CI/CD、Git、测试时路由到此。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.