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/jketreno/clare/verifygit clone --depth 1 https://github.com/jketreno/clareWrote 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/jketreno/clare/verify)<a href="https://agentmods.dev/commands/jketreno/clare/verify"><img src="https://agentmods.dev/badge/commands/jketreno/clare/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.00000 | $0.00302 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 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
/project:verify — Run CLARE verification
Runs ./clare/verify-ci.sh and reports a structured summary of results.
Instructions
Execute the following and report results clearly:
./clare/verify-ci.sh 2>&1
# Or to continue past failures and collect all results before reviewing:
./clare/verify-ci.sh --fail-slow 2>&1
After running:
- State clearly: PASSED or FAILED
- If failed, list each failing check by name
- For each failure, show the first few lines of the captured error output (the script prints a concise snippet). Include a suggested "quick command" the developer/agent can run to iterate on that specific failure (e.g.,
npx eslint --fix .,npx tsc --noEmit,pytest -q). - Propose specific fixes for each failure
- Offer to fix and re-run: "Shall I fix these issues and run verify again?"
Format
## Verify CI Results
Status: ✅ PASSED / ❌ FAILED
### Failing Checks
- **[Check name]**: [brief error description]
Fix: [specific action needed]
### Next Step
[Offer to fix and rerun, or confirm completion if passed]
If all checks pass, confirm: "All CI checks pass. Work is complete. Please review the diff and commit."
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 · 38 lines · 0 tokens per session scan A f5d83c2247b2
verify is a command published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 tokens. 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
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
remediate
Close the debt the deterministic lanes cannot version-bump away: the grandfathered broken build, advisories with no direct upgrade path, the lint backlog, missing tests, missing docs. Each run plans that debt as finite work orders and works them in two tiers: deterministic recipes execute first at $0 (lockfile resync…
reviewers
Suggest reviewers for a change, grounded on an active-owner model rather than a platform's naive last-touch blame.