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 commands/boussadjra/vuestrata/add-modulegit clone --depth 1 https://github.com/boussadjra/vuestrataWrote 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/commands/boussadjra/vuestrata/add-module)<a href="https://agentmods.dev/commands/boussadjra/vuestrata/add-module"><img src="https://agentmods.dev/badge/commands/boussadjra/vuestrata/add-module.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.00007 | $0.00190 |
| Opus 5 | $0.00003 | $0.00095 |
| Sonnet 5 | $0.00001 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
add-module 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.
What it actually says
Scaffold a domain module named $ARGUMENTS.
- Preview first:
vpr gen:module $ARGUMENTS --dry-run - If the plan looks right, run it without
--dry-run. - Read
docs/9.recipes/1.add-a-module.mdfor what the generator deliberately leaves to you. - Replace the placeholder schema in
src/modules/<name>/types.tswith the real domain shape — everything else in the module derives from it. - Verify:
vp check && vpr test --run
Do not hand-write the module files or the setup.ts / BuiltinPermission
registry entries; the generator handles those and forgetting them fails silently.
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 · 18 lines · 7 tokens per session scan A 5ad160867a3b
add-module is a command published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 5d ago), licensed MIT. It adds 7 tokens to every session and 190 once invoked, about $0.0000 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 commands, from other repositories
add-test
Command "add-test" from go4cas/quiver, covering step 1 — determine test type, step 2 — write unit tests (vitest), step 3 — write e2e tests (playwright) and step 4 — run and fix.
add-theme
Add a new visual theme to this Quiver app: $ARGUMENTS.
add-component
Create a new Quiver component named: $ARGUMENTS.
triage
Triage Linear issue with comprehensive analysis.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.