TigerGTC/opus-rail

Claude Code orchestration: Opus 4.8 drives, Opus 5 works. Hook-enforced or skill based workflow delegation and adversarial review.

2Stars on the repository
5Mods indexed here, across every type
2mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

executor

01

TigerGTC/opus-rail

Agent Claude Code

The DEFAULT destination for implementation in opus sessions: any coding, debugging, test-writing, or focused-review task that touches more than one trivial file goes here, per task, at the moment the work starts — not as an occasional escalation for large work. Runs Opus 5. Dispatch scoped: single objective, exact…

not rated 2 2mo ago C 111 tokens original MIT

planner

02

TigerGTC/opus-rail

Agent Claude Code

Plan and design drafter on Opus 5. The orchestrator dispatches it to author implementation plans, designs, and idea explorations as ADVISORY DRAFTS: it explores the change area (read-only), weighs alternatives, and returns a structured plan the orchestrator adjudicates against its fuller context. Default lane for…

not rated 2 2mo ago A 105 tokens original MIT

redteam

03

TigerGTC/opus-rail

Agent Claude Code

Adversarial reviewer on Opus 5. The orchestrator dispatches it against any idea, plan, design, architectural decision, or diff BEFORE presenting or committing it: attacks premises, steel-mans the strongest alternative, and names the likeliest failure mode. Read-only — returns findings, never edits. Not a general code…

not rated 2 2mo ago A 116 tokens original MIT

worker

04

TigerGTC/opus-rail

Agent Claude Code

Mechanical/bulk implementation, multi-file edits, and read-heavy search. Delegate here to keep bulk work on Sonnet and reserve Opus for judgment. Use for: repetitive edits across many files, boilerplate, mechanical refactors, running builds/tests, gathering file contents. Not for architectural decisions or judgment…

not rated 2 2mo ago C 71 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: