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/babushkai/claude-code-config/fix-issuenpx skills add babushkai/claude-code-config --skill fix-issuegit clone --depth 1 https://github.com/babushkai/claude-code-configWhat 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.00026 | $0.00221 |
| Opus 5 | $0.00013 | $0.00111 |
| Sonnet 5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
fix-issue 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 25 lines · 26 tokens per session scan A 6b38e4f2ef5b
fix-issue is a skill published in the GitHub repository babushkai/claude-code-config (10 stars, last pushed 5mo ago), with no licence file. It adds 26 tokens to every session and 221 once invoked, about $0.0001 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
reconcile
Enforces Law 1 (Research Before Executing) of the 7 Laws of AI Agent Discipline. Establishes git ground truth — branch, status, stashes, worktrees, ahead/behind — before any mutation, halts on protected or destructive operations, then carries the known-good state through to a landed PR: stage by filename, commit one…
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
pr
Commit all changes (if needed), push to remote, and create a GitHub pull request in one automated step with no prompts. Handles plan files automatically (renaming, moving completed plans to done). Use when the user says "pr", "create a pr", "open a pr", "submit a pr", "push and create pr", "commit and create pr", or…
commit
Create well-structured git commits with context-aware message generation, plan awareness, and support for common commit workflow variants. Use when the user says "commit", "commit the changes", "commit and push", "commit the plan", "commit staged", "commit just the staged changes", "give the plan a meaningful name and…
commit
Create a Conventional Commit safely. Guards against committing to main, validates format, stages and commits. Chains to push-and-pr when user mentions push. Triggers: "commit", "/commit", "закоммить", "сделай коммит", "коммит и пуш", "commit and push".
ship
Final pre-merge step — sync docs, then prepare a clean commit/PR summary. Use after verify passes. Does NOT commit or push unless you explicitly ask; it prepares everything and stops.