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.
git clone --depth 1 https://github.com/verivus-oss/llm-cli-gatewayWrote 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/verivus-oss/llm-cli-gateway/claude-request)<a href="https://agentmods.dev/commands/verivus-oss/llm-cli-gateway/claude-request"><img src="https://agentmods.dev/badge/commands/verivus-oss/llm-cli-gateway/claude-request/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/verivus-oss/llm-cli-gateway/claude-request"><img src="https://agentmods.dev/badge/commands/verivus-oss/llm-cli-gateway/claude-request.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00078 |
| Opus 5.5 | $0.00006 | $0.00031 |
| Sonnet 5.5 | $0.00003 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
claude-request 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 1mo 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
Send a request through the llm-gateway MCP server's claude_request tool.
Raw arguments: $ARGUMENTS
Use the llm-gateway's claude_request MCP tool to execute this prompt. Pass the raw arguments as the prompt.
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.
- 1mo ago First seen · 11 lines · 14 tokens per session scan A 02e28c9502d8
claude-request is a command published in the GitHub repository verivus-oss/llm-cli-gateway (16 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 78 once invoked, about $0.0001 per session on Opus 5.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
openspec-archive
Archive a deployed OpenSpec change and update specs.
modernize-assess
Full discovery & portfolio analysis of a legacy system — inventory, complexity, debt, effort estimation.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
modernize-brief
Generate a phased Modernization Brief — the approved plan that transformation agents will execute against.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
revise-claude-md
Update GEMINI.md with learnings from this session.