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.
git 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-component)<a href="https://agentmods.dev/commands/boussadjra/vuestrata/add-component"><img src="https://agentmods.dev/badge/commands/boussadjra/vuestrata/add-component.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.00149 |
| Opus 5 | $0.00003 | $0.00075 |
| Sonnet 5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
add-component 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 7d 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 component: vpr gen:component $ARGUMENTS
Pass --field for form fields — it also writes the
composables/forms/useUi<Name>.ts behaviour hook. The wrapper holds markup and
the data-ui theming hook; behaviour lives in the composable.
Colour must come from semantic tokens (bg-card, text-muted-foreground,
border-border). Raw palette utilities like bg-blue-500 are rejected by lint.
See docs/9.recipes/4.add-a-component.md. Verify: vp check && vpr test --run
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.
- 7d ago First seen · 16 lines · 7 tokens per session scan A 556a9a9bbac9
add-component is a command published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 7d ago), licensed MIT. It adds 7 tokens to every session and 149 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
quality-commands
:::info This document covers the code quality commands for validating comment standards and i18n completeness in the eIsland frontend. ::.
add-composable
Create a new Quiver composable named: $ARGUMENTS.
add-layout
Create a new Quiver layout named: $ARGUMENTS.
add-page
Create a new Quiver page for the route path: $ARGUMENTS.
add-state
Create a new Quiver state module for: $ARGUMENTS.
add-theme
Add a new visual theme to this Quiver app: $ARGUMENTS.