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 skills add the-metafactory/soma --skill vsagit clone --depth 1 https://github.com/the-metafactory/somaWrote 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/the-metafactory/soma/vsa)<a href="https://agentmods.dev/skills/the-metafactory/soma/vsa"><img src="https://agentmods.dev/badge/skills/the-metafactory/soma/vsa.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.1 | $0.00065 | $0.00929 |
| Opus 5 | $0.00032 | $0.00464 |
| Sonnet 5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
VSA 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 6d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VSA
The VSA is the document that articulates "done" for work whose ideal state is being pursued: a project, feature, library, infrastructure change, work session, art piece, or strategic decision. It acts as ideal-state articulation, test harness, done condition, verification record, and system of record.
Fast Path
- Identify the requested VSA workflow from the routing table below.
- Load only that workflow file from
Workflows/. - Load
references/format.mdonly when the task needs section, tier, ISC, or reconciliation rules. - Load
references/examples.mdonly when scaffolding or comparing against an exemplar. - Load
references/gotchas.mdbefore reconcile, tier checks, or any edit that might renumber criteria.
Do not load the full examples directory by default. Pick the smallest example that matches the task tier and domain.
When To Use
Use when the prompt mentions ideal state, VSA, ISC, ideal state criteria, project specification, articulating done, scaffolding an VSA, interviewing for an VSA, checking completeness, reconciling an ephemeral feature file back to a master VSA, or seeding an VSA from an existing project.
Do not use for creating new skills, running the Algorithm itself, generating non-VSA artifacts, postmortems, decision logs, or engineering journals. Those are retrospective; the VSA is a commitment-time scaffold.
Workflow Routing
When ambiguous, default to Scaffold for new VSAs and CheckCompleteness for audits.
| Intent | Workflow | Load |
|---|---|---|
| scaffold, create, generate, new VSA, extract feature as ephemeral | Scaffold | Workflows/Scaffold.md |
| interview me, fill in, deepen, ask questions | Interview | Workflows/Interview.md |
| check, audit, score, is this complete | CheckCompleteness | Workflows/CheckCompleteness.md |
| reconcile, merge feature file back, ephemeral to master | Reconcile | Workflows/Reconcile.md |
| seed, bootstrap from repo, draft from existing code | Seed | Workflows/Seed.md |
| append decision, append changelog, append verification, record C/R/L | Append | Workflows/Append.md |
What ships with it
21 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.
- Examples/canonical-vsa.md 18 KB
- Examples/e1-minimal.md 1.6 KB
- Examples/e2-backup-verify.md 5.5 KB
- Examples/e2-rotate-credential.md 5.5 KB
- Examples/e3-essay.md 13 KB
- Examples/e3-help-redesign.md 13 KB
- Examples/e3-project.md 4.1 KB
- Examples/e4-api-migration.md 25 KB
- Examples/e4-brand-identity.md 24 KB
- Examples/e5-album.md 21 KB
- Examples/e5-desktop-app.md 21 KB
- Examples/e5-enterprise.md 37 KB
- references/examples.md 1.5 KB
- references/format.md 4.6 KB
- references/gotchas.md 1.4 KB
- Workflows/Append.md 5.8 KB
- Workflows/CheckCompleteness.md 5.3 KB
- Workflows/Interview.md 4.5 KB
- Workflows/Reconcile.md 5.8 KB
- Workflows/Scaffold.md 6.0 KB
- Workflows/Seed.md 6.8 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.
- 6d ago First seen · 93 lines · 65 tokens per session scan A 39371c4e7582
VSA is a skill published in the GitHub repository the-metafactory/soma (8 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 929 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…