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/cptnbg/relay/relay-stopgit clone --depth 1 https://github.com/cptnbg/relayWrote 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/cptnbg/relay/relay-stop)<a href="https://agentmods.dev/commands/cptnbg/relay/relay-stop"><img src="https://agentmods.dev/badge/commands/cptnbg/relay/relay-stop.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.00112 |
| Opus 5 | $0.00008 | $0.00056 |
| Sonnet 5 | $0.00003 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
relay-stop 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.
This is a copy
81% identical to relay-doctor — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoke the relay skill (Skill tool) and follow its stop section.
Before running any relay script with Bash, resolve the plugin root exactly as the skill's "Resolve the plugin root" section specifies, and invoke scripts only through $RELAY_ROOT — never through a bare CLAUDE_PLUGIN_ROOT expansion. If the resolver prints "relay: FATAL", stop and tell the user to reinstall the plugin.
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 · 12 lines · 15 tokens per session scan A 303e594287a4
relay-stop is a command published in the GitHub repository cptnbg/relay (1 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 112 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to relay-doctor, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
cc-plan
(Conductor) Map implementation steps from an approved spec.
cc-init
(Conductor) Initialize or re-sync the project environment.
cc-review
(Conductor) Review code changes against spec and standards.
cc-docs
(Conductor) Audit and update project documentation.
cc-test
(Conductor) Analyze coverage gaps and write missing tests.
cc-refactor
(Conductor) Refactor a file or module for clarity and simplicity.