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 skills add nortonx/ai-tooling-free --skill update-claude-mdgit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/update-claude-md)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/update-claude-md"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/update-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/skills/nortonx/ai-tooling-free/update-claude-md"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/update-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.00034 | $0.00743 |
| Opus 5 | $0.00017 | $0.00371 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
update-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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
[<path-to-CLAUDE.md>]
- Optional. Explicit path to the CLAUDE.md to update; defaults to searching the repo root and
.claude/. - Examples:
/update-claude-md,/update-claude-md packages/api/CLAUDE.md
Copilot CLI note:
$ARGUMENTSdoesn't substitute in skills — include the argument inline in your prompt.
Update CLAUDE.md
Analyze recent branch changes and propose additions to the project's CLAUDE.md.
Scope
- Locate CLAUDE.md: Use
$ARGUMENTSas the path if provided; otherwise search the repo root and.claude/for aCLAUDE.mdfile. - Diff source: Changes between this branch and
main/master.
Task
- Read the current CLAUDE.md in full.
- Run
git diff main...HEAD(ormaster...HEAD) to get the branch diff. - Identify additions worth documenting — only stable, reusable conventions:
- New CLI commands, scripts, or tooling patterns introduced
- New architectural patterns or module conventions
- Non-obvious configuration or environment constraints
- Public API changes (new endpoints, changed contracts, new env vars)
- New dependencies and why they were added
- Gotchas, workarounds, or constraints discovered during the work
- Filter out:
- One-off fixes unlikely to recur
- Implementation details (function bodies, variable names)
- Anything already documented in CLAUDE.md
- Obvious information derivable from reading the code
Output
Show proposed additions as a diff — do not edit any files yet:
### Update: <path-to-CLAUDE.md>
**Why:** <one-line reason>
\`\`\`diff
+ <addition — one line per concept>
\`\`\`
Group by section if adding to multiple parts of the file. If nothing new is worth documenting, say so and explain why.
After showing the diff, ask: "Apply these changes?"
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 · 71 lines · 34 tokens per session scan A afd647e72ed7
update-claude-md is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 26d ago), licensed MIT. It adds 34 tokens to every session and 743 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
docs-sync
Keep project documentation in sync with code changes. Identifies which docs need updating after a PR merges or code changes, drafts the updates, and manages doc site structure (mkdocs, docusaurus, vitepress). Use when: (1) a PR just merged and docs may need updating, (2) the user says "update the docs" or "sync docs"…
project-planner
Triage ideas, problems, and feature requests into the right format: proposal doc, feature issue, or bug report. Repo-aware — discovers templates and docs structure from the current repository. Use when: (1) the user describes an idea, feature, or problem they want to track, (2) the user says "file a bug", "I have an…
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…
pg-migration
PostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…