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 skills add richardcb/oh-my-gemini --skill conductor-setupgit clone --depth 1 https://github.com/richardcb/oh-my-geminiWrote 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/skills/richardcb/oh-my-gemini/conductor-setup)<a href="https://agentmods.dev/skills/richardcb/oh-my-gemini/conductor-setup"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/conductor-setup.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.1 | $0.00047 | $0.01104 |
| Opus 5 | $0.00023 | $0.00552 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
conductor-setup 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Setup Skill
Goal
Initialize a complete Conductor workflow in the user's project with all necessary configuration files.
Activation Triggers
- User runs
/omg:setupor/omg:conductor-setup - User asks to "set up Conductor", "initialize workflow", or "enable planning"
- Project has no
conductor/directory and user wants structured development
Hook Integration
Conductor phase enforcement is now handled by the phase-gate hook:
- Advisory mode (default): Shows message at phase boundaries
- Strict mode: Blocks progression until user confirms
Setup now focuses on creating files; enforcement is automatic via hooks.
Bundled Resources
This skill includes all Conductor templates:
templates/product.md- Product context templatetemplates/tech-stack.md- Technology stack templatetemplates/workflow.md- Development workflow templatetemplates/tracks.md- Track listing templatetemplates/code_styleguides/general.md- General code style guide
Process
1. Check Existing Setup
ls -la conductor/ 2>/dev/null && echo "EXISTS" || echo "NOT_FOUND"
If Conductor already exists, ask user if they want to:
- Skip (keep existing)
- Merge (add missing files)
- Replace (overwrite all)
2. Create Directory Structure
mkdir -p conductor/tracks
mkdir -p conductor/code_styleguides
3. Gather Product Context
Ask the user:
- "What is this project? (one sentence)"
- "Who are the main users?"
- "What problem does it solve?"
4. Detect Tech Stack
Examine project files:
# Check for package.json (Node.js)
cat package.json 2>/dev/null | head -20
# Check for requirements.txt (Python)
cat requirements.txt 2>/dev/null | head -10
# Check for go.mod (Go)
cat go.mod 2>/dev/null | head -5
Ask user to confirm/correct detected stack.
5. Configure Hook Behavior (Optional)
Ask if they want to customize phase gate behavior:
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 173 lines · 47 tokens per session scan A 4df7e738ff16
conductor-setup is a skill published in the GitHub repository richardcb/oh-my-gemini (16 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,104 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 skills, from other repositories
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-shape
Shape a raw product or project idea into a bounded decision before planning or implementation. Use when deciding whether an idea deserves a bet, setting an appetite, comparing candidate bets under finite capacity, cutting scope, exposing rabbit holes and no-gos, or choosing BET, RESEARCH, RESHAPE, or PASS. This skill…
skill-runner
Run a bounded development task through named skills in an isolated, tmux-backed Codex or Claude session. Use for durable or artifact-sensitive worker phases, supervised skill runs, and post-run skill evaluation.
intuitive-doc
Create and maintain an intuitive human documentation surface for AI-agent-developed repos. Use when humans should only need README.md, ARCHITECTURE.md, STATUS.md, and docs/human/ while planning logs, generated docs, retrospectives, ADR detail, and implementation evidence stay in AI-agent-only folders.
create-migration
Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.