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 agents/tigergtc/opus-rail/executorgit clone --depth 1 https://github.com/TigerGTC/opus-railWhat 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.00111 | $0.00714 |
| Opus 5 | $0.00056 | $0.00357 |
| Sonnet 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 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.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 111 tokens to every session and 714 once invoked, about $0.0006 per session on Opus 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
polymath
Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.
hatch3r-creator
Authors user-tier custom artifacts (agents, skills, rules, commands, hooks) under .hatch3r/overrides/. Validates frontmatter schema, runs strict + gentle quality gates, and writes the artifact only when all strict gates pass.
hatch3r-context-rules
Context-aware rules engine that applies coding standards based on file type, location, and project conventions. Use when enforcing project rules on save or reviewing files against established patterns.
hatch3r-handoff-preparer
Prepare a canonical handoff document capturing mid-work session state. Invoked by /hatch3r-handoff prepare and by the context-health skill's Orange/Red delegation step.
data-engineer
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
dev
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.