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/koaning/wigglystuffWrote 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/koaning/wigglystuff/fix-issue)<a href="https://agentmods.dev/commands/koaning/wigglystuff/fix-issue"><img src="https://agentmods.dev/badge/commands/koaning/wigglystuff/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/commands/koaning/wigglystuff/fix-issue"><img src="https://agentmods.dev/badge/commands/koaning/wigglystuff/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.00000 | $0.00168 |
| Opus 5.5 | $0.00000 | $0.00067 |
| Sonnet 5.5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
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 yesterday.
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
Find and fix issue #$ARGUMENTS. Follow these steps:
Ultrathink and use the gh cli to pull in as much relevant context as necessary.
- Understand the issue described in the ticket (comments, associated PRs, etc)
- Locate the relevant code in our codebase
- Come up with a plan to create a test to reproduce the error (Test Driven Development) if it is possible and stop to check in with me
- Implement a solution that addresses the root cause
- Come up with a plan for testing if one was not already created and stop to check in with me
- Add appropriate tests (if confirmed by me)
- Prepare a concise PR description in
commit.md(follow style of .claude/commands/write-commit.md)
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.
- yesterday First seen · 12 lines · 0 tokens per session scan A 9db4ad682699
fix-issue is a command published in the GitHub repository koaning/wigglystuff (450 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 168 tokens. 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-10-14.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
tdd
Correction de Bug en Mode TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
qa
Validate an application against a Gherkin user story by spawning a QA team that drives the running app.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.
do-execute-qa-bugfix
Recebe o caminho de um arquivo de bug em qa-bugs/, analisa a causa raiz, implementa a correção com testes de regressão, valida a suite de testes e atualiza o status do arquivo. Invoque uma vez por bug.