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 agentmods add skills/megamen32/lasthumancommit/planningnpx skills add megamen32/LastHumanCommit --skill planninggit clone --depth 1 https://github.com/megamen32/LastHumanCommitWhat 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 | $0.00020 | $0.00348 |
| Opus 5 | $0.00010 | $0.00174 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
planning 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 2d 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
Planning
Use only when planning can materially reduce wrong-path or coordination cost.
Procedure
- Record the latest business outcome and accepted MVP Definition of Done.
- Trace the actual production consumer path.
- State the shortest real canary and cheapest sufficient proof.
- Rank direct Lead work and delegation by wall-clock, scarce quota, handoff, retry, human interruption, and wrong-path cost.
- Load
$task-decompositionwhen parallel or multi-cycle work remains. - Treat every 20 active minutes as a progress and route checkpoint, not an agent lifetime limit.
- Give every declared work cycle an immutable minimum/maximum estimate and run the business time guard at observable checkpoints; report every crossed hour and original-maximum overrun.
- Add governance only for a concrete risk whose expected loss exceeds gate cost.
- When a human route choice is useful, present exactly two genuinely different
approaches. For each, derive
ideal/full -> normal -> YAGNI/Pareto MVPand show only the compressed MVP, its discarded scope, advantages, disadvantages, time, and real canary. Recommend the least-cost YAGNI route by default.
Do not
- Do not present three ritual plans, technical previews, or architecture essays.
- Do not call ideal/normal/YAGNI three alternatives; they are one compression pass applied inside each of two different approaches.
- Do not forbid Lead implementation when it is cheaper.
- Do not replace a route decision with a larger estimate.
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.
- 2d ago First seen · 37 lines · 20 tokens per session scan A 5e8087e2744a
planning is a skill published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 348 once invoked, about $0.0001 per session on Opus 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
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…