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/voro6yov/spec-driven-development/convert-patternsnpx skills add voro6yov/spec-driven-development --skill convert-patternsgit clone --depth 1 https://github.com/voro6yov/spec-driven-developmentWhat 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.00052 | $0.00870 |
| Opus 5 | $0.00026 | $0.00435 |
| Sonnet 5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
convert-patterns 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a patterns-to-skills conversion orchestrator. Discover all pattern files, interview the user to collect metadata for each one they want to convert, then spawn skill-from-pattern agents in parallel.
Arguments
$ARGUMENTS[0]: path to the directory containing pattern files (searched recursively)$ARGUMENTS[1]: path to the plugin directory where skills will be added (e.g.,plugins/persistence-spec)
Workflow
Step 1 — Discover pattern files
Use Bash to find all .md files under $ARGUMENTS[0] recursively, sorted:
find "$ARGUMENTS[0]" -name "*.md" | sort
Display the results as a numbered list to the user, showing just the filename (not the full path) next to each number. Keep the full paths internally for later use.
Step 2 — Ask which patterns to convert
Use AskUserQuestion to ask:
"Found the patterns listed above. Which would you like to convert to skills? Enter numbers comma-separated (e.g.
1,3,5), orallto convert everything."
Parse the answer into a list of selected pattern file paths.
Step 3 — Interview per selected pattern
For each selected pattern, in order:
3a — Read the file
Read the pattern file. Extract:
- The title (first
#heading) — derive the suggested skill name (kebab-case, e.g.,Command Repository→command-repository) - The Purpose section — draft a one-line description:
<Pattern name> pattern for <domain>. Use when <trigger conditions>.
3b — Ask four questions, one at a time, using AskUserQuestion
Q1 — Skill name
"[] Skill name (kebab-case slug)? Suggested:
<suggested-name>Press Enter to accept."
If the user presses Enter or replies with nothing, use the suggested value.
Q2 — Description
"[] Skill description (one line for the frontmatter)? Suggested:
<suggested-description>Press Enter to accept."
If the user presses Enter or replies with nothing, use the suggested value.
Q3 — User-invocable
"[] Should
<skill-name>be user-invocable (callable as/<skill-name>)? [yes / no, default: no]"
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 · 109 lines · 0 tokens per session scan A 9c598ff7b8a6
convert-patterns is a skill published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 870 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-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…