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-codegit 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-code)<a href="https://agentmods.dev/skills/megamen32/lasthumancommit/worker-code"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/worker-code/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-code"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/worker-code.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.00083 | $0.00518 |
| Opus 5.5 | $0.00033 | $0.00207 |
| Sonnet 5.5 | $0.00017 | $0.00104 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
worker-code 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker Code
Implement one accepted business vertical. Lead owns route and integration.
Procedure
- Confirm the accepted outcome, actual consumer, allowed paths, exclusions, and cheapest sufficient proof.
- Search the reusable code map with the sibling Worker Research tool, then
verify relevant locations with targeted
rg. Do not repeat broad research already captured as fresh verified knowledge. - Trace the production call chain before editing an adjacent adapter, fixture, abstraction, or test double.
- Use the Ponytail shortcut without a ritual: omit speculative work; reuse existing code, stdlib, platform features or an installed dependency before writing the smallest new implementation that satisfies the accepted result.
- Run the real or closest claim-matching canary early. Fix only the first claim-blocking failure and add proportional direct-regression evidence.
- If the patch changes a durable production path, owner, or config location,
resolve
../worker-research/scripts/code_map.pyfrom this skill and upsert the affected key. Do not record ordinary task progress. - Stop when the assigned claim is proven.
Lead interaction
Ask Lead whenever its broader user context can change behavior, product choice, scope, proof strength, ownership, or a consequential action. Send concise evidence, recommendation/default, parallel-safe work, and the exact blocked action through a non-blocking parent transport; continue edits valid under every plausible answer.
At each 20-minute checkpoint report measured timing, changed files, business delta, blocker, whether the route remains shortest, and the smallest next action. The checkpoint redirects work; it does not kill the Worker.
Do not
- Do not implement horizontal completeness before the first usable path.
- Do not redesign, refactor, harden, document, or add compatibility work unless the current business claim requires it.
- Do not treat compilation or unit tests as user-facing proof.
- Do not trust a graph, context index, code map, or old task card over current source and the latest user outcome.
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 · +2 lines 6da77ccb0513
- 1mo ago First seen · 47 lines · 83 tokens per session scan A 016b1c2bc793
worker-code is a skill published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 518 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…