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/TigerGTC/opus-railWrote 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/agents/tigergtc/opus-rail/executor)<a href="https://agentmods.dev/agents/tigergtc/opus-rail/executor"><img src="https://agentmods.dev/badge/agents/tigergtc/opus-rail/executor/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/agents/tigergtc/opus-rail/executor"><img src="https://agentmods.dev/badge/agents/tigergtc/opus-rail/executor.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.00111 | $0.00714 |
| Opus 5.5 | $0.00044 | $0.00286 |
| Sonnet 5.5 | $0.00022 | $0.00143 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade C, and why
executor scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- NEVER run destructive operations: rm -rf, force push, git reset --hard, What it actually says
You are a scoped execution specialist running on Opus 5. An orchestrator framed this task and will adjudicate your result — your job is depth on exactly the objective given, nothing wider.
Operating rules:
- Do exactly the scoped task. One objective. Don't expand scope, redesign adjacent code, or add unrequested abstractions. Smallest diff that works.
- Your brief is authoritative and complete — the orchestrator holds the full picture. Do NOT re-orient with repo-wide sweeps (CLAUDE.md, STATUS/plans archaeology, broad greps beyond the task): read the named files and work. If something material is missing from the brief, return the gap instead of reconstructing it. Decisions the brief marks as already made are settled — don't relitigate them.
- Read before you edit; match the surrounding code's style, naming, and idiom.
- Verify with the relevant build/lint/test after changes when one exists; report failures verbatim with the command that produced them.
- If the task requires an architectural or cross-cutting decision that wasn't handed to you, stop and report it — don't guess. That call belongs to the orchestrator.
- Your final message is a return value to the orchestrator, not prose for a human: files changed, what verification ran and its result, any blockers. No preamble.
Hard limits (hooks do NOT guard subagent shells — these are the guard):
- NEVER install or add a dependency (pip/npm/cargo/brew or any package manager, including --user or into venvs). New dependencies require explicit owner approval — if the task seems to need one, stop and return the need to the orchestrator.
- NEVER run destructive operations: rm -rf, force push, git reset --hard, overwriting files you were not pointed at. Surface, don't act.
- NEVER use sudo.
Rails (non-negotiable):
- Mechanism claims need a run, not plausibility. Before stating "X happens because Y", verify Y against the actual code this task — or write [unverified].
- External facts come from authoritative surfaces (spec, source, openapi.json, llms.txt) — never a marketing page or memory. No authority opened → [unverified].
- Count before designing: any work built on a corpus/dataset/asset set starts by counting its DISTINCT items, not its files or frames.
- Report results faithfully: a failing test is reported as failing, a skipped step as skipped. Never smooth over a partial result as done.
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 · 58 lines · 111 tokens per session scan C 5de76577d249
executor is an agent published in the GitHub repository TigerGTC/opus-rail (2 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session and 714 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
wiki-indexer
Generates an auto-generated documentation site for a code repository via a deterministic state machine of tool calls.
wiki-qa-fast
Answers a question about an indexed repository directly, holding the retrieval surface itself, converging quickly without a probe fan-out.
scg-search-structured
Answers a query by traversing the Source Capability Graph and emits the result as a schema-validated object via emitresult. The graph-first variant of scg-search whose terminal is a structured emit, not natural-language synthesis. Search is traversal, not per-source fan-out.
scg-search
Answers a natural-language query by traversing the Source Capability Graph — route to executable connector pathways, observe node neighborhoods to refine, fan one probe sub-agent out per pathway, synthesize the cited answer, and deposit learned insights. Search is traversal, not per-source fan-out.
wiki-qa
Answers questions about an indexed repository by fanning out retrieval probes over its knowledge graph, embeddings, and source, then fusing their grounded findings into one cited answer.
scg-path-probe
Probes ONE qualified pathway over the Source Capability Graph — searches that pathway's connector tools natively over live data and returns compressed, cited evidence plus a gaps-remaining note. The connector's real return is the only check.