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/fradser/dotclaude/ask-mattnpx skills add FradSer/dotclaude --skill ask-mattgit clone --depth 1 https://github.com/FradSer/dotclaudeWrote 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/fradser/dotclaude/ask-matt)<a href="https://agentmods.dev/skills/fradser/dotclaude/ask-matt"><img src="https://agentmods.dev/badge/skills/fradser/dotclaude/ask-matt.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.00050 | $0.03292 |
| Opus 5 | $0.00025 | $0.01646 |
| Sonnet 5 | $0.00010 | $0.00658 |
| Haiku 4.5 | $0.00005 | $0.00329 |
Grade A, and why
ask-matt 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Matt
You don't remember every skill, so ask.
A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.
The main flow: idea → ship
The route most work travels. You have an idea and want it built.
-
/mattpocock:grill-with-docs— sharpen the idea by interview. Start here when you have a codebase: it's stateful, retaining what it learns inCONTEXT.mdand ADRs. (No codebase? Use/mattpocock:grill-me— see Standalone. Both run the same/mattpocock:grillingprimitive;grill-with-docsis the one that leaves a paper trail.) -
Branch — can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by
/mattpocock:handoffin both directions (see Crossing sessions):/mattpocock:handoffout, then open a fresh session against that file,/mattpocock:prototypeto answer the question with throwaway code,/mattpocock:handoffback what you learned, and reference it from the original idea thread.
-
Branch — is this a multi-session build?
- Yes →
/mattpocock:to-spec(turn the thread into a spec), then/mattpocock:to-ticketsto split it into tracer-bullet tickets, each declaring its blocking edges. On a local tracker that's one file per ticket under.scratch/<feature>/issues/, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed — kick off/mattpocock:implementper ticket, clearing context between each one. - No →
/mattpocock:implementright here, in the same context window.
Either way,
/mattpocock:implementbuilds each issue by driving/mattpocock:bddinternally (Discovery → Formulation, then Automation delegated to/mattpocock:tdd) — one vertical slice at a time — then closes out by running/mattpocock:code-review, a two-axis review (Standards + Spec) of the diff, before committing. Reach for/mattpocock:bddon its own when you want to define Gherkin scenarios for a feature, and/mattpocock:tddon its own when you want to write tests within the BDD Automation phase. Reach for/mattpocock:code-reviewon its own whenever you want to review a branch or PR against a fixed point. - Yes →
What ships with it
2 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.
- 4d ago First seen · 98 lines · 50 tokens per session scan A 358ed34dbe26
ask-matt is a skill published in the GitHub repository FradSer/dotclaude (588 stars, last pushed 23d ago), licensed MIT. It adds 50 tokens to every session and 3,292 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.
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…