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 worker-bugfixgit 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/worker-bugfix)<a href="https://agentmods.dev/skills/megamen32/lasthumancommit/worker-bugfix"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/worker-bugfix/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/worker-bugfix"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/worker-bugfix.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.00087 | $0.00478 |
| Opus 5.5 | $0.00035 | $0.00191 |
| Sonnet 5.5 | $0.00017 | $0.00096 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
worker-bugfix 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
Worker Bugfix
Fix one proven failure without turning it into a hardening project.
Procedure
- Mandatory TDD for every bugfix. Before changing production source, write and run a focused regression that fails for the reported behavior. Record the exact failing command and its Red result, then rerun it Green after the smallest fix. A live/black-box failure is additional consumer evidence, never a substitute for this regression.
- Search the reusable code map for the symptom, consumer, and prior
failure-shieldentries. Check freshness and verify decisive locations with targetedrg. - Reproduce the real failure with the focused Red regression and, when the claim is user-facing, the cheapest safe consumer canary.
- Trace the failing consumer path and reject nearby but unused adapters or fixtures.
- Change the smallest coherent source slice that makes the same proof green.
- If the root cause or false route is likely to recur, resolve
../worker-research/scripts/code_map.pyfrom this skill and upsert a compactfailure-shieldentry with verified locations and the discriminating probe. Replace or remove knowledge invalidated by the fix. - Stop when the accepted behavior claim is proven.
Ask Lead non-blockingly instead of guessing when product intent, accepted fallback, data migration, blast radius, or proof strength changes the fix. Continue only answer-independent work while waiting.
Do not
- Do not widen the fix into cleanup, abstraction, security hardening, logging, compatibility, or exhaustive edge cases.
- Do not create a fake-contract test when a real consumer probe is cheaper and stronger.
- Do not claim production or UI recovery from source tests alone.
- Do not keep retrying after two failed hypotheses; report evidence and the shortest changed route to Lead.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · -1 lines 7997071b8830
- 1mo ago First seen · 41 lines · 87 tokens per session scan A bcf05b179877
worker-bugfix is a skill published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 478 once invoked, about $0.0003 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.