Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/boussadjra/vuestratanpx agentmods add commands/boussadjra/vuestrata/verifyWrote 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/verify)<a href="https://agentmods.dev/commands/boussadjra/vuestrata/verify"><img src="https://agentmods.dev/badge/commands/boussadjra/vuestrata/verify.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.00008 | $0.00208 |
| Opus 5 | $0.00004 | $0.00104 |
| Sonnet 5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
verify 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
Run the gates that match the change, cheapest first. Report actual output; do not claim success you have not seen.
Always:
vp check # format, lint, types
node scripts/lint/run-custom-rules.mjs # six project rules
vpr test --run # includes test/unit/architecture/
Add when relevant:
- routing, layouts, config, providers or runtime wiring changed →
vpr build - user-visible flow or routing changed →
vpr test:e2e - docs, env or UI copy changed →
node scripts/docs/check-links.mjs - module
mockHandlersor demo/production wiring touched →vpr buildthennode scripts/build/verify-bundle.mjs --mode=production
Note: test/component/users/user-management-components.test.ts has 7
pre-existing failures on main. They are not yours unless you touched that area.
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 · 26 lines · 8 tokens per session scan A 4684d0933512
verify is a command published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 208 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.
plugin-commands
:::info This document covers all build, test, and smoke commands for eIsland native plugins. Each plugin lives under plugins/ and has its own package.json with independent scripts. ::.
test-commands
:::info This document covers the testing commands for running, filtering, and measuring test coverage in the eIsland frontend. ::.
paul:verify
Guide manual user acceptance testing of recently built features.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.