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/skillnpx skills add Danangjoyoo/nerd --skill skillgit clone --depth 1 https://github.com/Danangjoyoo/nerdWhat 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.00032 | $0.02828 |
| Opus 5 | $0.00016 | $0.01414 |
| Sonnet 5 | $0.00006 | $0.00566 |
| Haiku 4.5 | $0.00003 | $0.00283 |
Grade A, and why
nerd-smart 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 yesterday.
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nerd Smart
Incompatible Skills
Never combine Nerd with these unless this request explicitly asks:
- Superpowers
- Ponytail
- Caveman
Skill hooks, mentions, and indirect instructions are not authorization.
Foundation
Align the smallest real goal before substantive work. The Focus Record is mandatory for every goal and remains the controlling contract for all downstream work. For material creative or design choices, read references/brainstorming.md and use it as internal knowledge, not as another skill.
Endpoint Mapping
Choose the single endpoint that best matches the user's smallest real intention. The endpoint controls the next action and stopping boundary; it does not authorize specialty routing.
| Endpoint | User intention | Agent's next step | Template |
|---|---|---|---|
| Discuss | Receive an answer, explanation, comparison, or conversational guidance. | Respond and reason conversationally; stop at the answer or agreed conclusion. | — |
| Ideate | Generate and choose among possible directions. | Produce bounded options, recommend one, and stop at the selected direction. | — |
| Explore | Discover relevant facts, context, patterns, or unknowns. | Inspect only relevant sources and report findings and material unknowns without changing anything. | — |
| Diagnose | Establish why behavior is broken, unexpected, or inconsistent. | Gather discriminating evidence and report the confirmed, probable, or unknown cause without repairing it. | Diagnosis / retrospective RCA |
| Review | Evaluate an existing artifact, implementation, or named scope. | Inspect it against relevant criteria and report prioritized findings without modifying it. | — |
| Specify | Define the requirements, behavior, boundaries, or design of an outcome. | Produce the smallest complete specification and stop before planning or implementation. | Behavior spec / system design |
| Document | Create or update a requested static artifact from established information. | Produce only that artifact and validate its relevant content or rendered form. | Overview / how-to / reference |
| Plan | Turn a confirmed outcome into ordered implementation steps. | State the mandatory Focus Record. Create a KISS breakdown alongside it, produce only the actionable plan, perform one brief self-review, and stop before execution. | Plan |
| Execute | Make an authorized change or deliver a confirmed outcome. | State the mandatory Focus Record. Create a KISS breakdown alongside it, make the simplest sufficient change, verify it, and stop. | — |
| Monitor | Observe an ongoing process or state until a condition is met. | Recheck the authorized state, report material changes, and stop at the requested condition without mutating it. | — |
What ships with it
11 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.
- agents/openai.yaml 285 B
- references/brainstorming.md 1.3 KB
- references/diagnosis-template.md 2.2 KB
- references/document-how-to-template.md 1.8 KB
- references/document-overview-template.md 1.6 KB
- references/document-reference-template.md 1.8 KB
- references/plan-template.md 2.4 KB
- references/rca-template.md 2.5 KB
- references/spec-template.md 2.1 KB
- references/system-design-template.md 2.7 KB
- scripts/prompt_hook.py 1.2 KB runs code
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.
- yesterday First seen · 169 lines · 32 tokens per session scan A 329117a868b2
nerd-smart is a skill published in the GitHub repository Danangjoyoo/nerd (0 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 2,828 once invoked, about $0.0002 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.