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/rayforcedb/raysense/verifygit clone --depth 1 https://github.com/RayforceDB/raysenseWhat 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.00025 | $0.00153 |
| Opus 5 | $0.00013 | $0.00077 |
| Sonnet 5 | $0.00005 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
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 yesterday.
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 that recent edits in $1 have not regressed structural health.
If $1 is empty, treat the project root as the current working directory.
- Call
raysense_rescanwithpath: $1to refresh the live scan and trend log. - Call
raysense_baseline_diffwithpath: $1to compare the current scan against the saved baseline.
Report deltas only: rules that newly tripped, files that became hot, dimensions that worsened. If nothing regressed, say so explicitly.
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.
- yesterday First seen · 14 lines · 25 tokens per session scan A e34d457dedf9
verify is a command published in the GitHub repository RayforceDB/raysense (11 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 153 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
brooks-audit
Run a Brooks-Lint architecture audit.
deploy
Deploy Solana program (devnet first, then mainnet).
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.