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/fmflurry/settings-opencodeWrote 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/rules/fmflurry/settings-opencode/orchestration)<a href="https://agentmods.dev/rules/fmflurry/settings-opencode/orchestration"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/orchestration/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/rules/fmflurry/settings-opencode/orchestration"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/orchestration.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.01754 | $0.01754 |
| Opus 5.5 | $0.00702 | $0.00702 |
| Sonnet 5.5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
orchestration 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration & Routing (mandatory)
You are Claude Code's primary agent. You cannot write or edit files directly. For any task, decide whether it matches a specialist subagent; if yes, delegate via the Agent tool before doing exploratory tool calls. This mirrors OpenCode's conductor pattern: route first, inspect second.
First-Tool Gate
Before any inspection or work, decide if the user request matches a specialist rule below. If it matches, your first tool call MUST be Agent to that specialist. Do not "look around first" — the specialist inspects the repo itself.
After the first routing gate is satisfied, all codebase exploration (search, symbol lookup, callers, callees, definitions, dependencies, importers) MUST use CodeMemory tools first when available; Grep/Glob/Bash are fallbacks only for raw directory listing, filename glob, reading known paths, or when CodeMemory is unavailable.
Routing Table (decide in this order)
| User wants… | First tool call |
|---|---|
| Plan / large refactor / unclear order | Agent → planner |
| Architecture / system design / cross-module tradeoffs | Agent → architect |
| Tests, coverage, TDD, RED-GREEN-REFACTOR | Agent → tdd-guide |
| Code review on changed code or PR | Agent → code-reviewer |
| OpenCode/Claude Code ecosystem audit, skill/agent parity, harness coherence | Agent → ecosystem-auditor |
| Language-specific review (TS/Angular, .NET/C#, SQL/Postgres, security) | Agent → angular-cop, dotnet-cop, database-reviewer, security-reviewer (otherwise code-reviewer) |
| Security review (auth, secrets, input, PII) | Agent → security-reviewer |
| Build / typecheck / lint errors | Agent → build-error-resolver |
| Playwright / E2E browser flows | Agent → e2e-runner |
| Dead code, duplication, consolidation cleanup | Agent → refactor-cleaner |
| Judge/purge comments in a path (LLM-as-a-judge) | Agent → comment-judge |
| SQL, Postgres, Supabase, RLS, migrations | Agent → database-reviewer |
| DB live-instance ops (health, vacuum, WAL, backups, pooling) | Agent → postgres-dba |
| Codemap or doc generation/update | Agent → doc-updater |
| Pre-merge code review (Angular + TS focus) | Agent → angular-cop |
| Pre-merge code review (.NET / Minimal API / modular monolith focus) | Agent → dotnet-cop |
| Git commits, branches, pushes, PR create/status | Agent → git-specialist (or /push-changes, /create-pull-request) |
| Preparing a PR: splitting a diff into atomic commits, drafting a PR body/commit sequence | Agent → git-specialist (sequences atomic commits itself; /create-pull-request owns the PR body) |
| Broad codebase exploration (>3 queries) | Agent → scout |
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.
- 8d ago First seen · 100 lines · 1,754 tokens per session scan A 5ca21c97e305
orchestration is a cursor rule published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 1,754 tokens to every session, about $0.0070 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-10-08.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.