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 mouchegmouradian/claude-code-skills --skill skill-improvementgit clone --depth 1 https://github.com/mouchegmouradian/claude-code-skillsWrote 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/mouchegmouradian/claude-code-skills/skill-improvement)<a href="https://agentmods.dev/skills/mouchegmouradian/claude-code-skills/skill-improvement"><img src="https://agentmods.dev/badge/skills/mouchegmouradian/claude-code-skills/skill-improvement/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/mouchegmouradian/claude-code-skills/skill-improvement"><img src="https://agentmods.dev/badge/skills/mouchegmouradian/claude-code-skills/skill-improvement.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.00141 | $0.01219 |
| Opus 5 | $0.00071 | $0.00609 |
| Sonnet 5 | $0.00028 | $0.00244 |
| Haiku 4.5 | $0.00014 | $0.00122 |
Grade A, and why
skill-improvement 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Improvement
This skill captures knowledge gained during a working session and feeds it back into the relevant skill — keeping skills accurate and up to date without manual maintenance.
When to trigger
Trigger this skill whenever, during a session, you observe any of the following:
- A skill's instructions were incomplete or wrong and you had to correct course
- You discovered an edge case the skill didn't cover
- The user corrected you in a way that implies a skill gap
- A fix, workaround, or pattern emerged that should be documented for next time
- The user explicitly says "update the skill", "add this to the skill", etc.
- At natural session wrap-up points when a skill was actively used — proactively check if anything is worth capturing, even if the user didn't mention it
Don't wait to be asked. If you notice something, surface it.
Skill repo location
The skills git repo is at: ~/Projects/claude-code-skills/
Skills source lives at: ~/Projects/claude-code-skills/skills/
The ~/.claude/skills/ directory contains symlinks into the above.
The improvement flow
Step 1 — Identify and summarize the gap
When you detect an improvement opportunity, pause and tell the user:
"I noticed something worth capturing in the [skill-name] skill: [one-sentence description of the gap or fix]. Want me to propose a patch?"
Keep it brief. Don't write the patch yet.
Step 2 — Draft the patch
If the user says yes (or "go ahead", "sure", etc.), draft the minimal change to SKILL.md:
- Show a unified diff or clearly marked before/after block
- Keep changes surgical — fix only what was wrong, don't refactor unrelated sections
- If adding new content, place it in the most logical existing section rather than appending at the end
- If the change is substantial, briefly explain your reasoning
Then ask:
"Does this look right, or would you like to adjust anything before I commit it?"
Step 3 — Apply and commit (only after explicit approval)
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.
- 12d ago First seen · 138 lines · 141 tokens per session scan A 427e517f1ebc
skill-improvement is a skill published in the GitHub repository mouchegmouradian/claude-code-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 141 tokens to every session and 1,219 once invoked, about $0.0007 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
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
ship
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
stage
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
commit-staged-push
Commit already-staged changes and push in one step. Use when the user asks to "commit and push staged changes", "commit and push what's staged", or "commit staged and push".