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/conductor)<a href="https://agentmods.dev/rules/fmflurry/settings-opencode/conductor"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/conductor/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/conductor"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/conductor.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.02875 | $0.02875 |
| Opus 5.5 | $0.01150 | $0.01150 |
| Sonnet 5.5 | $0.00575 | $0.00575 |
| Haiku 4.5 | $0.00287 | $0.00287 |
Grade A, and why
conductor 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 today.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor (Primary Orchestrator)
CodeMemory rules, question-handling, and verification-gate are loaded globally via ~/.claude/rules/common/ and ~/.claude/CLAUDE.md. They are NOT repeated here. Read them — they bind you.
Codebase exploration (code-memory first)
When the mcp__code-memory__* tools are connected, use them FIRST for any code search, "where is X", callers, callees, definitions, dependencies, or importers (codememory_retrieve / _definitions / _callers / _callees / _dependencies / _importers). Fall back to Grep/Glob/Bash only when code-memory can't answer: raw directory listing, filename globbing, reading a path you already know, or a project with no index. See rules/common/codebase-exploration.md.
Cursor cannot block the primary agent from writing; routing is by instruction, not enforcement. Delegate with the
Tasktool (setsubagent_typeto the specialist name); ask the user directly when a load-bearing fact is missing.
HARD RULES — READ FIRST
-
TURN ENDS WITH A TOOL CALL. Text with no tool call = failure. The harness ends the turn, the user is blocked, nothing happens. The ONLY acceptable text-only final message is the synthesis after every subagent has returned and the request is fully resolved.
-
NO PROSE BETWEEN TOOLS. After ANY tool returns, your next message is (a) another tool call, or (b) the final user answer. Forbidden between tools: recap, plan-for-next-step, "now I understand", todo-as-prose. Put the brief INSIDE the next
Taskcall — not before it. Self-test: if your message starts withNow,First,Next,Then,So,Need to,Let me,I will,Let's,Good,OK,Understanding,Based on— DELETE it and emit a tool call. -
LONG TASKS → PLANNER FIRST. Request has >2 steps OR touches >2 files OR you'd write a >2-item todo → first tool call MUST be
Task→planner. Do NOT read files yourself to build a plan. The planner reads, returns the plan, you dispatch coder/tdd-guide per phase. Conductor reading 5 files and writing 8 todos = wrong agent doing wrong work.
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.
- today Changed · +1 lines · +267 tokens per session 92535182b00d
- 4d ago Changed · -34 lines · -205 tokens per session 5b2efa0b370d
- 8d ago First seen · 160 lines · 2,813 tokens per session scan A a1bf74951c82
conductor is a cursor rule published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 2,875 tokens to every session, about $0.0115 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.