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/Habib0x0/spec-driven-pluginWrote 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/habib0x0/spec-driven-plugin/spec-verify)<a href="https://agentmods.dev/commands/habib0x0/spec-driven-plugin/spec-verify"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-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.
<a href="https://agentmods.dev/commands/habib0x0/spec-driven-plugin/spec-verify"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-verify.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00898 |
| Opus 5.5 | $0.00006 | $0.00359 |
| Sonnet 5.5 | $0.00003 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
spec-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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-verify Command
Run smoke tests against a deployed environment to verify the feature works in production/staging. Reuses the spec-tester agent with a target URL instead of localhost.
Philosophy
"It works on my machine" doesn't count. Post-deployment verification catches environment-specific issues: missing env vars, CORS misconfigs, database connectivity, CDN caching, etc. This is a lightweight check, not a full test suite — just enough to confirm the feature is alive.
Workflow
1. Locate the Spec
If a spec name is provided, use it. Otherwise auto-detect from .claude/specs/.
2. Get the Target Environment
If a URL was provided as a second argument, use it. Otherwise, ask via AskUserQuestion:
- Production — Enter the production URL
- Staging — Enter the staging URL
- Custom environment — Enter any URL
Also ask:
- Full smoke test — Verify all acceptance criteria that can be tested via browser
- Quick health check — Just verify the app loads and key routes respond
- Specific requirements — Pick which requirements to verify
3. Build the Smoke Test Plan
Read requirements.md and extract acceptance criteria that can be verified via browser/HTTP:
- UI behaviors → Playwright navigation and interaction
- API endpoints → HTTP requests to verify responses
- Authentication flows → Login/logout verification
- Error handling → Verify error pages/responses work
Skip criteria that require:
- Database state manipulation (unless safe read-only checks)
- Background job verification
- Internal-only metrics
4. Spawn the Tester Agent
Delegate to the spec-driven:spec-tester agent via the Task tool.
Pass the agent:
- The spec directory path
- The target URL (NOT localhost)
- The testing scope (full, quick, or specific)
- Instruction to treat this as a smoke test, not a full test suite — verify the feature exists and responds correctly, don't test every edge case
- Instruction to not modify any code or files — this is read-only verification
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.
- 1mo ago First seen · 117 lines · 14 tokens per session scan A 462ac6581b7e
spec-verify is a command published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 898 once invoked, about $0.0001 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-31.
Other commands, from other repositories
generate-tests
Generate unit, integration, and e2e test suites from scaffolded project with framework-appropriate coverage.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
spec-check
Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.