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/obsidian-owl/specwright/sw-verifygit clone --depth 1 https://github.com/Obsidian-Owl/specwrightWrote 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/obsidian-owl/specwright/sw-verify)<a href="https://agentmods.dev/commands/obsidian-owl/specwright/sw-verify"><img src="https://agentmods.dev/badge/commands/obsidian-owl/specwright/sw-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 | $0.00043 | $0.00068 |
| Opus 5 | $0.00022 | $0.00034 |
| Sonnet 5 | $0.00009 | $0.00014 |
| Haiku 4.5 | $0.00004 | $0.00007 |
Grade A, and why
sw-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 3d 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
Use the installed specwright:sw-verify skill for this request.
$ARGUMENTS
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.
- 3d ago First seen · 8 lines · 43 tokens per session scan A 0480cd51bf51
sw-verify is a command published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 68 once invoked, about $0.0002 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-31.
Other commands, from other repositories
implement-python-tool
Implement a Python tool using a specialized Haiku-powered agent.
quick-fix
Launch Quick Fix Agent (Haiku) for fast bug fixes and minor improvements.
review-pr
Launch the Code Review and Fix Agent (Sonnet) to perform comprehensive code review.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.
paul:help
Show available PAUL commands and usage guide.
brooks-audit
Run a Brooks-Lint architecture audit.