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/microsoft/hve-core/dt-methodsnpx skills add microsoft/hve-core --skill dt-methodsgit clone --depth 1 https://github.com/microsoft/hve-coreWhat 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.00055 | $0.01401 |
| Opus 5 | $0.00028 | $0.00700 |
| Sonnet 5 | $0.00011 | $0.00280 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
dt-methods 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Thinking Methods Skill
Entrypoint for Design Thinking method coaching knowledge. The dt-coach agent loads the method reference matching the active method in coaching state, the matching deep reference when advanced technique is needed, and the industry reference when an industry context applies.
How to use this skill
- Read the method reference for the method currently active in coaching state to ground day-to-day coaching.
- Read the matching deep reference when the conversation needs advanced facilitation, recovery techniques, or expert frameworks beyond the core method guidance.
- Read the industry reference when the team has identified one of the nine covered industries as their context, and weave its vocabulary, constraints, and empathy tools into method-specific guidance.
- Read dt-coach-telemetry.md when DT session artifacts need observable telemetry expectations grounded in
telemetry-foundations.
Method references
| Method | Name | Core reference | Deep reference |
|---|---|---|---|
| 1 | Scope Conversations | method-01-scope.md | method-01-deep.md |
| 2 | Design Research | method-02-research.md | method-02-deep.md |
| 3 | Input Synthesis | method-03-synthesis.md | method-03-deep.md |
| 4 | Brainstorming | method-04-brainstorming.md | method-04-deep.md |
| 5 | User Concepts | method-05-concepts.md | method-05-deep.md |
| 6 | Low-Fidelity Prototypes | method-06-lofi-prototypes.md | method-06-deep.md |
| 7 | High-Fidelity Prototypes | method-07-hifi-prototypes.md | method-07-deep.md |
| 8 | User Testing | method-08-testing.md | method-08-deep.md |
| 9 | Iteration at Scale | method-09-iteration.md | method-09-deep.md |
What ships with it
28 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.
- references/dt-coach-telemetry.md 1.5 KB
- references/industry-energy.md 9.1 KB
- references/industry-financial-services.md 11 KB
- references/industry-healthcare.md 7.7 KB
- references/industry-manufacturing.md 6.7 KB
- references/industry-nonprofit-social-impact.md 16 KB
- references/industry-pharmaceuticals-life-sciences.md 20 KB
- references/industry-professional-services.md 14 KB
- references/industry-public-sector.md 12 KB
- references/industry-retail-cpg.md 17 KB
- references/method-01-deep.md 10 KB
- references/method-01-scope.md 10 KB
- references/method-02-deep.md 16 KB
- references/method-02-research.md 7.1 KB
- references/method-03-deep.md 14 KB
- references/method-03-synthesis.md 8.9 KB
- references/method-04-brainstorming.md 14 KB
- references/method-04-deep.md 16 KB
- references/method-05-concepts.md 17 KB
- references/method-05-deep.md 18 KB
- references/method-06-deep.md 16 KB
- references/method-06-lofi-prototypes.md 17 KB
- references/method-07-deep.md 11 KB
- references/method-07-hifi-prototypes.md 9.8 KB
- references/method-08-deep.md 15 KB
- references/method-08-testing.md 11 KB
- references/method-09-deep.md 17 KB
- references/method-09-iteration.md 12 KB
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 · 87 lines · 55 tokens per session scan A 19cacfd4a863
dt-methods is a skill published in the GitHub repository microsoft/hve-core (1,411 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,401 once invoked, about $0.0003 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-30.
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.