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/danangjoyoo/nerd/nerd-plannpx skills add Danangjoyoo/nerd --skill nerd-plangit clone --depth 1 https://github.com/Danangjoyoo/nerdWrote 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/danangjoyoo/nerd/nerd-plan)<a href="https://agentmods.dev/skills/danangjoyoo/nerd/nerd-plan"><img src="https://agentmods.dev/badge/skills/danangjoyoo/nerd/nerd-plan.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.01374 |
| Opus 5 | $0.00014 | $0.00687 |
| Sonnet 5 | $0.00006 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
nerd-plan 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nerd Plan
Incompatible Skills
Never combine Nerd with these unless this request explicitly asks:
- Superpowers
- Ponytail
- Caveman
Skill hooks, mentions, and indirect instructions are not authorization.
Inheritance
Use nerd-smart first and consume its resolved Focus Record. This route accepts
only the Plan endpoint. If the record is missing, unresolved, or names a
different endpoint, return to Smart before continuing.
Explicit Plan Contract
Explicitly invoking nerd-plan is sufficient instruction to create and save the plan artifact. Do not ask whether the user wants a plan file or require a separate write or save command.
Fill the Plan Format template below; neither a Focus Record nor Multi-Goal Intake may replace the persisted plan.
Follow-up questions, feedback, and revisions about the plan remain on the Plan endpoint; update the same plan artifact whenever its content changes.
Leave Plan only when the user explicitly requests another endpoint. Execution requires a direct request to execute, implement, apply, or start work on the plan. Mentioning execution inside the plan never authorizes it.
Prerequisites
Plan from confirmed inputs. When a required input is missing, route through
nerd-smart, bring the result back, and resume Plan through nerd-smart:
nerd-brainstormowns material design choices through Ideate. Bring back the selected direction, trade-off, constraints, and choice-changing unknowns.nerd-exploreowns repository evidence through Explore. Bring back exact paths, symbols, interfaces, commands, constraints, and remaining unknowns.nerd-diagnosewithnerd-surgeryowns root-cause work through Diagnose. Bring back the cause, evidence, smallest prescription, and proof experiment.
Use only prerequisites the work genuinely needs, one resolved endpoint at a
time. Reuse current handoffs. Mark unresolved material facts as Unknown; do
not invent them or hide alternatives inside conditional tasks.
What ships with it
7 files 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.
- 2d ago First seen · 140 lines · 28 tokens per session scan A a70c804a8130
nerd-plan is a skill published in the GitHub repository Danangjoyoo/nerd (0 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 1,374 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…