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/dimkurilo/opencode-skills/vs-architectnpx skills add dimkurilo/opencode-skills --skill vs-architectgit clone --depth 1 https://github.com/dimkurilo/opencode-skillsWrote 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/dimkurilo/opencode-skills/vs-architect)<a href="https://agentmods.dev/skills/dimkurilo/opencode-skills/vs-architect"><img src="https://agentmods.dev/badge/skills/dimkurilo/opencode-skills/vs-architect.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.00073 | $0.01208 |
| Opus 5 | $0.00036 | $0.00604 |
| Sonnet 5 | $0.00015 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
vs-architect scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Verification:** VS analysis — user selected a relevant variant. Execution — test command (curl, test, run) How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Architect — Agent Instructions
Two-Phase Workflow
PHASE 1: VS Analysis
Distribution prompt → k variants with probabilities → user selects
PHASE 2: Execution Prompt
Selected variant → detailed implementation prompt (no VS)
Step 0: Input Validation
- Task context present (3+ facts: task/constraints/what was tried/files/prompt) → proceed. Any format is valid.
- No input or < 15 words → ask: "Describe the task in detail: what needs to be done, constraints, what you've already tried."
PHASE 1: VS Analysis
Step 1: Classification
Classify the input along 4 axes (see references/vs-theory.md, Classification Axes section). Set UNKNOWN for missing axes.
Present classification to user and request confirmation before proceeding to Step 2:
TASK CLASSIFICATION:
- Complexity: [TRIVIAL | MODERATE | UNCERTAIN]
- Type: [CODE | STRATEGY | DIAGNOSTIC | CREATIVE | DATA]
- Variants: [FEW | MANY | SINGLE]
- Constraints: [YES | NO]
Confirm? If not — specify what to adjust.
Step 2: Pattern Selection
Apply Decision Tree from references/vs-theory.md. Check rules strictly top-to-bottom; first match wins.
Step 3: Execution Mode Selection
Apply Mode Mapping from references/vs-theory.md.
Additional rules:
- Complex mode → first tool call must be read-only (Assumption Checkpoint)
- 25+ tool calls → Business Outcome Verification pause
- ≥2 external systems with unverified API contracts → Pro
- Subagent task() calls → append 【思维模式要求】 injection
Step 4: VS Prompt Construction
Use the template from references/vs-theory.md (Prompt Templates section) for the selected pattern.
Parameters:
- k (variant count): default 5. D → 5 (many rounds). B → 5. C → 3–5
- Probability threshold: B → p < 0.10 (diversity) or p > 0.5 (stability)
- Output format: headers + sections (human-readable), JSON (subagent)
- Language: preserve user's input language
- Do not use XML tags — headers are equally readable
PHASE 2: Execution Prompt
What ships with it
7 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.
- 3d ago First seen · 150 lines · 73 tokens per session scan A 3c6f096a26e6
vs-architect is a skill published in the GitHub repository dimkurilo/opencode-skills (6 stars, last pushed 21d ago), licensed MIT. It adds 73 tokens to every session and 1,208 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…