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/eshwarvijay/secondmate/secondmate-verifygit clone --depth 1 https://github.com/eshwarvijay/secondmateWhat 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.00032 | $0.00177 |
| Opus 5 | $0.00016 | $0.00088 |
| Sonnet 5 | $0.00006 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
secondmate-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 2d 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 secondmate verify-gate and report PASS or the exact REFUSE reasons. Do NOT integrate/merge unless it PASSes.
Arguments (worktree path, base branch, and the SHA the checker reviewed): $ARGUMENTS
Execute (fill the values from the arguments; add --test "<cmd>" if a test command applies):
"${CLAUDE_PLUGIN_ROOT}/bin/verify-gate.sh" --worktree <worktree> --base <branch> --checked-sha <sha>
Passing --checked-sha (the exact commit the checker reviewed) is mandatory — it catches a maker
pushing new commits after the checker approved.
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.
- 2d ago First seen · 17 lines · 32 tokens per session scan A 5b79b01c0ee5
secondmate-verify is a command published in the GitHub repository eshwarvijay/secondmate (3 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 177 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
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
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.
brain-stats
Show claudectl brain learning metrics — accuracy, correction rate, and effectiveness.
cost-tracker
Track session costs, understand token spend, and get optimization tips.