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/deephaven/deephaven-mcp/skill-addnpx skills add deephaven/deephaven-mcp --skill skill-addgit clone --depth 1 https://github.com/deephaven/deephaven-mcpWrote 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/deephaven/deephaven-mcp/skill-add)<a href="https://agentmods.dev/skills/deephaven/deephaven-mcp/skill-add"><img src="https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/skill-add.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.00071 | $0.01666 |
| Opus 5 | $0.00036 | $0.00833 |
| Sonnet 5 | $0.00014 | $0.00333 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
skill-add 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add an Agent Skill
End-to-end workflow for creating a new skill at .agents/skills/<name>/SKILL.md. Wraps ref-skill-authoring-standards (structure) + ref-skill-effectiveness (content) + ref-agents-md-curation (decide whether the content belongs in AGENTS.md instead).
A new skill that no parent invokes is invisible. The Composition gate at step 2 is the most important step — run it before drafting anything.
Steps
-
Decide reference vs workflow. Apply
ref-skill-authoring-standardsNaming and the prefix rule. A workflow is a verb-noun action a human invokes directly. A reference is a noun-phrase standards document loaded by other skills. -
Composition gate. Required first design step.
- Search the catalog
.agents/skills/README.mdfor an existing skill that already covers this concern. If found, edit that skill instead. Stop here. - Identify which existing skills the new skill will invoke (its children).
- Identify which existing skills will invoke the new skill (its parents).
- If the new skill would have exactly one parent and no independent trigger, it is a section of that parent. Inline it; do not create a new file.
- Apply
ref-skill-authoring-standardsComposition is the architecture extraction and merge triggers.
- Search the catalog
-
Decide skill vs
AGENTS.mdvs both. Applyref-agents-md-curationWhat belongs inAGENTS.mdand What does NOT belong inAGENTS.md. If the content fits both, pick the single source of truth and decide which file points to which. -
Pick the name and prefix. Apply
ref-skill-authoring-standardsNaming and the prefix rule. The prefix rule answers one question: will any human ever invoke this skill directly? If yes (even occasionally), no prefix — even if other skills also reference it. If no, prefix withref-.- The
namemust be lowercase letters, numbers, and hyphens only, at most 64 characters, and identical to the directory name. The spec rejects anything else. - A
ref--prefixed skill also carriesuser-invocable: false(ref-skill-authoring-standardsFrontmatter contract). Unprefixed workflows omit the key.
- The
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 · 64 lines · 71 tokens per session scan A 713aa8bca6de
skill-add is a skill published in the GitHub repository deephaven/deephaven-mcp (5 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 1,666 once invoked, about $0.0004 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…