A command guide for checking code after a change. It selects checks such as formatting, linting, type checking, tests, builds, end-to-end tests, link checks, and production-bundle verification based on what changed.

Use it after changing code, routes, layouts, configuration, runtime wiring, documentation, environment settings, user interfaces, or mock and production integrations.

It prevents claiming that a change works without seeing the relevant checks pass. It also notes a known group of test failures that already exists on the main branch.

How boussadjra/vuestrata configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to boussadjra/vuestrata. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/boussadjra/vuestrata/main/.claude/commands/verify.md

Clone the repo

git clone --depth 1 https://github.com/boussadjra/vuestrata

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/boussadjra/vuestrata/verify/github.svg)](https://agentmods.dev/commands/boussadjra/vuestrata/verify)

Your own site

<a href="https://agentmods.dev/commands/boussadjra/vuestrata/verify"><img src="https://agentmods.dev/badge/commands/boussadjra/vuestrata/verify/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/boussadjra/vuestrata/verify"><img src="https://agentmods.dev/badge/commands/boussadjra/vuestrata/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 208 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00003	$0.00083
Sonnet 5.5	$0.00002	$0.00042
Haiku 4.5	$0.00001	$0.00021

Measured 2mo ago against content hash 4684d0933512, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/verify.md · 26 lines

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 mockHandlers or demo/production wiring touched → vpr build then node 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.

Changes

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.

2mo ago First seen · 26 lines · 8 tokens per session scan A 4684d0933512

Subscribe to this mod's changes

verify is a command published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 11d ago), licensed MIT. It adds 8 tokens to every session and 208 once invoked, about $0.0000 per session on Opus 5.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.

E2E testing Testing TypeScript tailwindcss vite vitejs vuejs vuejs3

verify next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
verifyboussadjra/vuestrata	Command	111	11d ago	MIT	A	8	Claude Code
e2e-testingJNTMTMTM/eIsland	Command	335	yesterday	GPL-3.0	A	0	Claude Code
add-testgo4cas/quiver	Command	5	26d ago	MIT	A	0	Claude Code
plugin-commandsJNTMTMTM/eIsland	Command	335	yesterday	GPL-3.0	A	0	Claude Code
test-commandsJNTMTMTM/eIsland	Command	335	yesterday	GPL-3.0	A	0	Claude Code
ui-snapshot.templateevan043/claude-cli-advanced-starter-pack	Command	61	3mo ago	MIT	A	0	Claude Code
test-rundesplega-ai/qa-use	Command	29	1mo ago	MIT	A	0	Claude Code

vuestrata: Command for Claude Code