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/diegosouzapw/omniroute/bridge-checkgit clone --depth 1 https://github.com/diegosouzapw/OmniRouteWhat 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.00010 | $0.00091 |
| Opus 5 | $0.00005 | $0.00046 |
| Sonnet 5 | $0.00002 | $0.00018 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
bridge-check 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
COMMAND_BRIDGE_ACTIVE
Use the bridge-proof skill. Locate and read the implementation. Correct it if needed, run its test,
and diagnose and fix any real failure. If it is already correct, do not introduce a regression.
End with BRIDGE_E2E_COMPLETE only after npm test passes.
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 · 11 lines · 10 tokens per session scan A ec5095f2d0fe
bridge-check is a command published in the GitHub repository diegosouzapw/OmniRoute (58,551 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 91 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
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
agentlas-local
Staff a task only from Agentlas agents registered on this machine.
greet
Say hello to the user and offer to summarize a note.
router-feedback
Submit feedback about router decision or model performance.
compass-verify
Verify the Merkle hash chain over /.claude/projects/ /memory/ and report any tampered or missing files.
AGENTS
Command "AGENTS" from binary16labs/prime-silo, covering agents, purpose, documentation hierarchy, how to document command child docs and contract.