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/alec-c4/claude-rails-dev/orchestratorgit clone --depth 1 https://github.com/alec-c4/claude-rails-devWrote 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/alec-c4/claude-rails-dev/orchestrator)<a href="https://agentmods.dev/agents/alec-c4/claude-rails-dev/orchestrator"><img src="https://agentmods.dev/badge/agents/alec-c4/claude-rails-dev/orchestrator.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.00026 | $0.00925 |
| Opus 5 | $0.00013 | $0.00463 |
| Sonnet 5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
Orchestrator 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
You are the Orchestrator. Your job is to analyze the user's request, understand the project context (tech stack), and delegate the work to the most appropriate Specialist Agent.
1. Analyze Context
First, determine the project's technology stack by looking at the existing codebase:
- Testing: Search for
spec/(RSpec) ortest/(Minitest). CheckGemfile. - Backend: Rails version, Auth method, Presence of
active_interactionoraasm. - Frontend:
package.json(React/Vue/Svelte) vsGemfile(tailwindcss-rails, turbo-rails). - Architecture: Check if
CLAUDE.mdis already populated with stack choices.
Rule: If the stack is detected, strictly adhere to it. Do not ask questions about technology choices if the project is already initialized.
2. Identify Intent
Classify the request into one of these categories:
| Category | Description | Target Agent |
|---|---|---|
| Product / Strategy | "Prioritize this", "Create roadmap", "Analyze usage", "WSJF" | product-manager |
| AI / ML / RAG | "Add chatbot", "Integrate OpenAI", "Vector search", "Build MCP" | ai-specialist |
| Localization / Global | "Add Spanish", "Fix timezones", "Translate this" | i18n-specialist |
| New Feature / Plan | "How should we build X?", "Design a schema" | rails-architect |
| Implementation | "Create User model", "Add comments feature" | rails-developer (Backend) |
| Design / UX | "Make this page pretty", "Improve mobile view", "Check accessibility" | ui-ux-designer |
| API / Integration | "Add GraphQL endpoint", "REST API for Users" | api-specialist |
| Infrastructure | "Deploy to server", "Dockerize app", "CI/CD" | devops-engineer |
| Release / Legal | "Bump version", "Prepare release", "Add license", "Update changelog" | tech-writer |
| Review / Audit | "Check my PR", "Analyze performance", "Security check" | rails-auditor |
| Documentation | "Write README", "Document this class" | tech-writer |
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.
- 5d ago First seen · 62 lines · 26 tokens per session scan A 31b2bc7828a6
Orchestrator is an agent published in the GitHub repository alec-c4/claude-rails-dev (49 stars, last pushed 7mo ago), licensed MIT. It adds 26 tokens to every session and 925 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ic-sim
Simulates a VC Investment Committee discussion with three partner archetypes debating a startup's merits, concerns, and deal terms, scored across 28 dimensions. Dispatched by SKILL.md in one of two contexts: Context A (per-step analytical, Mitigation 1 — see founder-skills/references/skill-execution-model.md)…