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/ebibibi/ebi-agent-chat-relay/verifygit clone --depth 1 https://github.com/ebibibi/ebi-agent-chat-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/ebibibi/ebi-agent-chat-relay/verify)<a href="https://agentmods.dev/commands/ebibibi/ebi-agent-chat-relay/verify"><img src="https://agentmods.dev/badge/commands/ebibibi/ebi-agent-chat-relay/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.00156 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
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 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.
What it actually says
Run the full verification pipeline before committing:
- Run
uv run ruff check claude_discord/— fix any lint errors - Run
uv run ruff format claude_discord/— ensure formatting - Run
uv run pytest tests/ -v --cov=claude_discord --cov-report=term-missing— all tests must pass - Run a security scan: search for
shell=True, hardcoded secrets, and unvalidated user input in the codebase - Verify the public API imports work:
python -c "from claude_discord import ClaudeRunner, ClaudeChatCog"
Report results for each step. If any step fails, fix the issue and re-run that step before proceeding.
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 · 10 lines · 0 tokens per session scan A 31f6d3015df2
verify is a command published in the GitHub repository ebibibi/ebi-agent-chat-relay (57 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 156 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-30.
Other commands, from other repositories
work
Implement a scv/promote/ / plan. Reads PLAN.md + TESTS.md, proposes/loads Related Documents as needed, runs the tests, and optionally archives on success. Use whenever the user wants an existing plan implemented — 'build it', 'implement the plan', 'let's do it' — not only when they type /scv:work. Never implement a…
caspian-toast
Dummy — fire an OpenCode toast to test UI.
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
status
Show raw changes since last index + list of active promote plans. Use whenever the user asks what is in flight, what changed, or where things stand — not only when they type /scv:status. Never summarize project state from memory; this command reads it.
review
Run a Codex Router code review against local git state.
update
Check installed SCV plugin version vs latest release, and guide the user through /plugin marketplace update + /reload-plugins. Read-only — does not modify project files. (v0.11.2+) Use whenever the user asks whether SCV is current or how to update it — not only when they type /scv:update.