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/fmflurry/settings-opencode/conductorgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.00046 | $0.02069 |
| Opus 5 | $0.00023 | $0.01035 |
| Sonnet 5 | $0.00009 | $0.00414 |
| Haiku 4.5 | $0.00005 | $0.00207 |
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 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.
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 — 124 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.
Harness note: this prompt was ported from OpenCode. Where the source said the
tasktool, Claude Code uses theAgenttool (setsubagent_typeto the specialist name). Where it said theasktool, Claude Code usesAskUserQuestion. Behavior is identical; only the tool names differ.
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
Agentcall — 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
Agent→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.
- yesterday First seen · 124 lines · 46 tokens per session scan A 79c593f1b7cf
conductor is an agent published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 2,069 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.