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/mshadmanrahman/pm-pilot/verifygit clone --depth 1 https://github.com/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/verify)<a href="https://agentmods.dev/commands/mshadmanrahman/pm-pilot/verify"><img src="https://agentmods.dev/badge/commands/mshadmanrahman/pm-pilot/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.00015 | $0.00108 |
| Opus 5 | $0.00008 | $0.00054 |
| Sonnet 5 | $0.00003 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
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 4d 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
/verify
Run verification loop: build, test, lint.
Usage
/verify {optional: specific check}
Behavior
- Run build and check for errors
- Run test suite and report failures
- Run linter if configured
- If any step fails, attempt fix and re-verify (max 3 attempts)
- Report final status: all green or remaining issues
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.
- 4d ago First seen · 20 lines · 15 tokens per session scan A 503aabea9afc
verify is a command published in the GitHub repository mshadmanrahman/pm-pilot (19 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 108 once invoked, about $0.0001 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
workflow-from-spec
Design a complete multi-agent workflow from a natural language description, selecting the right orchestration pattern.
commit
Run when user calls /commit or asks to generate a commit message. Analyzes staged changes and writes a structured commit message.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
implement-tasks
执行实现任务，支持条件 TDD 工作流（代码使用 TDD，文档/配置直接实现）.
config
以交互方式管理 CodexSpec 项目配置.
intent
Press-release intent lifecycle — status, quoted-text create, the implement-readiness gate, and the human planning interview that turns a draft into a planned, specced intent.