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.
git clone --depth 1 https://github.com/Jewgah/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/commands/jewgah/claude-code-skills/fix)<a href="https://agentmods.dev/commands/jewgah/claude-code-skills/fix"><img src="https://agentmods.dev/badge/commands/jewgah/claude-code-skills/fix/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/commands/jewgah/claude-code-skills/fix"><img src="https://agentmods.dev/badge/commands/jewgah/claude-code-skills/fix.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.00019 | $0.00277 |
| Opus 5.5 | $0.00008 | $0.00111 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
fix 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.
What it actually says
Bug: $ARGUMENTS
If a referenced agent isn't installed in this repo (minimal tier), do that step yourself inline — never fail on a missing agent.
- Reproduce / locate — dispatch the
exploreragent to find the responsible code and trace the path. If a repro command exists, run it. - Root cause — identify the actual cause, not the symptom. State it in one line before fixing.
- Fix — dispatch the
implementeragent for the minimal correct fix. - Verify — dispatch the
testeragent to run{{TEST_CMD}}and confirm the bug is gone and nothing regressed. - Guard — quick
reviewerpass if the fix touches anything risky.
Report the root cause, the fix (path:line), and the test result. Don't commit unless I ask.
Then append a Dispatch report: Why this config (which agents you ran and why that depth fit the bug), a table Agent | Why popped | What it did | Result (one row per agent), and Skipped (agents you didn't use, and why).
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 · 19 lines · 19 tokens per session scan A f0012f72120a
fix is a command published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 10d ago), licensed MIT. It adds 19 tokens to every session and 277 once invoked, about $0.0001 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-31.
Other commands, from other repositories
check
Drift detector. Diff SPEC.md against code. Read-only, zero writes.
verify
Perform a systematic second-pass verification of code changes to catch errors before commit.
sniff-locate
List findings in .sniff/findings.jsonl, validate anchors, reanchor stale findings when code shifts, and regenerate .sniff/index.json.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
cc-review
(Conductor) Review code changes against spec and standards.