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 megamen32/LastHumanCommit --skill bugfix-tddgit clone --depth 1 https://github.com/megamen32/LastHumanCommitWrote 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/megamen32/lasthumancommit/bugfix-tdd)<a href="https://agentmods.dev/skills/megamen32/lasthumancommit/bugfix-tdd"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/bugfix-tdd/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/megamen32/lasthumancommit/bugfix-tdd"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/bugfix-tdd.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.00046 | $0.00270 |
| Opus 5.5 | $0.00018 | $0.00108 |
| Sonnet 5.5 | $0.00009 | $0.00054 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
bugfix-tdd 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
Bugfix red/green
For new assignments, load worker-bugfix; it supersedes this compact alias with
reusable failure-shield and rg guidance.
Use for a bounded behavior failure where a discriminating failing proof is worth its setup cost.
Procedure
- Trace the real failing consumer path.
- Capture the smallest safe failing regression, existing check, or black-box canary that distinguishes the symptom.
- Implement the smallest coherent fix on that path.
- Re-run the same proof and proportional direct-regression checks.
- Stop when the accepted claim is proven.
- Ask Lead instead of guessing at a context-dependent business decision; use a non-blocking parent transport and continue answer-independent work when available.
Do not
- Do not write a new unit test when an existing or real canary is cheaper and stronger.
- Do not widen the fix into hardening, cleanup, abstraction, or edge-case work.
- Do not claim a user-facing result from a build alone.
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 · 32 lines · 46 tokens per session scan A 6f718833931b
bugfix-tdd is a skill published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 270 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.