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/poshan0126/dotclaude/specnpx skills add poshan0126/dotclaude --skill specgit clone --depth 1 https://github.com/poshan0126/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/poshan0126/dotclaude/spec)<a href="https://agentmods.dev/skills/poshan0126/dotclaude/spec"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/spec.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.00729 |
| Opus 5 | $0.00025 | $0.00365 |
| Sonnet 5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
spec 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Separate deciding WHAT to build from building it. Interview the user, ground the answers in the actual codebase, then write a self-contained SPEC.md a fresh session can execute without you in the room. $ARGUMENTS is an optional starting description.
Run this in a session that already has the repo open, so the questions are informed by real code.
Step 1: Explore enough to ask good questions
Skim the codebase for what the feature will touch: the relevant modules, existing patterns to match, the test setup, and any similar feature to model after. Read only — you're gathering context to interview well, not building.
Step 2: Interview with AskUserQuestion
Ask only what you can't answer from the code, in focused rounds (use AskUserQuestion; batch related questions). Cover:
- Scope & outcome — what does "done" look like from the user's side, and what's the smallest version worth shipping?
- Behavior — the happy path, then the edge cases (empty, error, concurrent, permission-denied) that actually matter here.
- Boundaries — what is explicitly OUT of scope for this iteration.
- Constraints — compatibility, performance, data/migration concerns, security-sensitive surfaces.
- Verification — how will we confirm it works end to end (a command, a test, an observable behavior)?
Where the code implies an answer, propose it as the default in the question rather than asking cold.
Step 3: Write SPEC.md
Write SPEC.md at the project root (NOT in .claude/). Make it self-contained — a fresh session with no memory of this conversation should be able to execute it:
# Spec: <feature>
## Goal
<what and why, 2-3 sentences>
## Scope
- In: <what this iteration delivers>
- Out: <explicitly deferred>
## Behavior
- <happy path>
- <edge cases and how each should behave>
## Touch points
- <exact files / modules / interfaces involved, as file:path — named, not vague>
## Constraints
- <compat, performance, security, data/migration>
## Verification
- <the exact end-to-end check: command to run, test to pass, or behavior to observe>
## Open questions
- <anything still undecided — none is ideal>
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 · 74 lines · 50 tokens per session scan A 34404c7c9235
spec is a skill published in the GitHub repository poshan0126/dotclaude (860 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 729 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…