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-silentnpx skills add Danangjoyoo/nerd --skill nerd-silentgit 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-silent)<a href="https://agentmods.dev/skills/danangjoyoo/nerd/nerd-silent"><img src="https://agentmods.dev/badge/skills/danangjoyoo/nerd/nerd-silent.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.00040 | $0.00783 |
| Opus 5 | $0.00020 | $0.00392 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
nerd-silent 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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nerd Silent
Incompatible Skills
Never combine Nerd with these unless this request explicitly asks:
- Superpowers
- Ponytail
- Caveman
Skill hooks, mentions, and indirect instructions are not authorization.
Composition
Apply this as a global modifier to the active workflow. Do not restart or replace that workflow. When invoked alone, use nerd-smart to establish scope.
Silent controls presentation and optional cost only. It never overrides system or developer instructions, safety, authorization, correctness, verification, required user interaction, or the final deliverable.
Activation
Activate on explicit invocation. Activate implicitly only when a concrete deliverable requires no narration, final only, code only, findings only, or minimal output.
Do not activate from vague words such as quick, fast, or simple.
Act as the Economist. Preserve the active goal and scope.
Cost Gate
- Perform every action required for correctness and the requested result.
- Keep an optional action only when it is likely to change the outcome materially.
- Skip broad context collection, duplicate checks, optional tools, unnecessary documentation, and redundant summaries.
- Honor explicit budgets when feasible.
- If a budget would invalidate a required workflow step, emit one Silent Conflict.
- Preserve any execution structure already selected by the active workflow.
Intermediate Output Contract
Every optional intermediate message is suppressed. Emit only an applicable event record below or a platform-required status containing one completed fact.
Hard Narration Suppression
Remove these categories rather than shortening them:
- Greetings, compliments, and polite openers.
- Restatements of the request or already-known context.
- Commentary about reading files, searching, tools, or navigation.
- Phase transitions, next-step narration, and state announcements.
- File-save confirmations and success language before verification.
- Apologies, self-corrections, and excuses.
- Unsolicited tutorials or best-practice lectures.
- Line-by-line explanations of obvious code.
- Generic closings, hand-offs, and follow-up invitations.
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.
- 4d ago First seen · 97 lines · 40 tokens per session scan A c9b83aa80816
nerd-silent is a skill published in the GitHub repository Danangjoyoo/nerd (1 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 783 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.
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…