Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.claude/skills/improve-claude-md/SKILL.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmindhub/packmind/improve-claude-md)<a href="https://agentmods.dev/skills/packmindhub/packmind/improve-claude-md"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/improve-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/packmindhub/packmind/improve-claude-md"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/improve-claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00092 | $0.02292 |
| Opus 5.5 | $0.00037 | $0.00917 |
| Sonnet 5.5 | $0.00018 | $0.00458 |
| Haiku 4.5 | $0.00009 | $0.00229 |
Grade A, and why
improve-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 1mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md Improver
Audit and improve the CLAUDE.md files this run owns, create the ones that are missing, then report
what changed.
You are running NON-INTERACTIVELY in CI: no human is available to confirm anything. Never ask a question — either apply a change that is clearly correct, or skip it and say so in the final summary. Apply fixes directly to the files as you go.
These are standing instructions for the whole run, not a one-time checklist.
Step 1 — Build the skill inventory
Before touching any CLAUDE.md, list every skill available in this repository.
Use Glob with the pattern **/.claude/skills/**/SKILL.md. Match at any depth: a .claude/skills
directory can itself live in a sub-directory, and skills may be nested. Ignore any hit under
node_modules. Ignore this skill (improve-claude-md) — it is CI tooling, not a
developer convention, so it never justifies deleting anything.
For each remaining SKILL.md, collect only the YAML frontmatter name and description. Do not
read skill bodies at this stage — inlining them wastes the context you need for the audit itself.
Then state the count out loud, for example Loaded frontmatter for 10 skill(s), and list the paths.
This line matters: a regression that silently empties the inventory (a gitignored .claude/skills, a
narrowed checkout, a changed glob) must be visible in the run log instead of quietly degrading into
"skip deduplication".
If the inventory is empty, say so explicitly and skip Step 5 (deduplication) entirely for the whole run.
Step 2 — Read the worklist
Read tmp/claude-md-worklist.txt. It holds one repository-relative CLAUDE.md path per line, and
it is authoritative: the workflow resolved it for this repository, and the scope differs between
repositories on purpose. In the open-source repository it is every CLAUDE.md in the tree; in the
proprietary fork it is only the packages that do not exist upstream, because every shared file is
owned by the other repository's run of this same workflow. Editing a file outside the worklist
diverges it between the two repositories and conflicts on the next sync.
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.
- 1mo ago First seen · 171 lines · 92 tokens per session scan A 2bb7fdee34b3
improve-claude-md is a skill published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 92 tokens to every session and 2,292 once invoked, about $0.0004 per session on Opus 5.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-30.
Other skills, from other repositories
ce-compound
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md. Use when capturing a learning after work.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.