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 smartwhale8/claude-playbook --skill fix-issuegit clone --depth 1 https://github.com/smartwhale8/claude-playbookWrote 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/smartwhale8/claude-playbook/fix-issue)<a href="https://agentmods.dev/skills/smartwhale8/claude-playbook/fix-issue"><img src="https://agentmods.dev/badge/skills/smartwhale8/claude-playbook/fix-issue/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/smartwhale8/claude-playbook/fix-issue"><img src="https://agentmods.dev/badge/skills/smartwhale8/claude-playbook/fix-issue.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.00035 | $0.00436 |
| Opus 5.5 | $0.00014 | $0.00174 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 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
Fix issue $ARGUMENTS
The issue
!gh issue view $ARGUMENTS 2>&1 || echo "Could not read issue $ARGUMENTS. Check the number and that gh is authenticated."
Workflow
-
Understand. Read the issue above. If the expected behaviour is ambiguous, ask before writing code. A wrong fix costs more than a question.
-
Reproduce. Find the failing behaviour in the code. Do not proceed on a theory you have not confirmed.
-
Plan. State the root cause and the change you intend, before editing. If the cause is unclear, say so instead of guessing.
-
Branch.
git switch -c fix/<short-description>. Never commit to the default branch. -
Test first. Write a test that fails because of this bug. Run it and watch it fail. A regression test that never failed proves nothing.
-
Fix. Address the cause. If the fix spans several files, explain why in the pull request.
-
Verify. Run the new test, then the full suite, then lint and type checks. Paste what the commands returned. Never assert success without the output.
-
Commit and open the pull request. Reference the issue. The description covers what changed, why, how it was verified, and any risk.
Rules
- The root cause, never the symptom. If the first idea is a workaround, keep looking.
- Do not change anything the issue did not ask for.
- If the fix turns out to need a decision that is not yours to make, stop and report what you found.
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 Changed · +14 lines · +21 tokens per session ddf3dad5e763
- 1mo ago First seen · 24 lines · 14 tokens per session scan A 901bf053ce6e
fix-issue is a skill published in the GitHub repository smartwhale8/claude-playbook (43 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 436 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-30.
Other skills, from other repositories
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims.
checkpoint
Save all work, update memory, commit, push, and prepare to end the session. Use when user says "save my work", "wrap up", or "I'm done for now". Use at natural breakpoints or when context is getting large.
create-project
Scaffold a new project with git, .gitignore, CLAUDE.md, AGENTS.md, GitHub repo, and memory directory. Use when user says "start a new project", "create a repo", or "scaffold an app". Creates the project as a sibling to the .claude/ config directory.
fix-issue
Investigates and fixes a GitHub issue. Use when given an issue number or URL, or when the user says 'fix issue'.
resolve-conflicts
Resolves an in-progress git merge or rebase conflict by recovering each side's intent from commits, PRs, and issues. Use when a merge or rebase stops on conflicts, or when the tree contains conflict markers.
dev-fix
Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.