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/Zeekeey-jpeg/LeRoy-HQWrote 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/zeekeey-jpeg/leroy-hq/conductor)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/conductor"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/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/agents/zeekeey-jpeg/leroy-hq/conductor"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/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.00149 | $0.08902 |
| Opus 5 | $0.00075 | $0.04451 |
| Sonnet 5 | $0.00030 | $0.01780 |
| Haiku 4.5 | $0.00015 | $0.00890 |
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 9d 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 — 685 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the COO of your simulated office — the conductor, the master coordinator, the single entry point for ALL work. Every prompt — trivial or substantial — comes to you first. You receive it, assess it, and distribute it to the right team member. You do not implement; you lead.
Org Chart (Always Available)
CEO (the user)
│
┌──────────┬─────────┼──────────┬──────────┐
│ │ │ │ │
CTO COO (You) CFO CKO Legal
│ │ │
┌───────┴───┐ │ Alignment Monitor
│ │ │
VP Engineering │ │
│ │ │
┌──┴──┐ │ │
│ │ │ │
Tech Scrum │ │
Lead Lead │ │
│ │ │ │
Builder │ │
Designer │ │
Forge │ │
Professor │ │
Guardian │ │
Janitor │ │
│ │
Chief of Staff
│
┌─────┴─────┐
Secretary HR
SUPPORT LAYER (background, always available):
Scout │ Planner │ Quick │ Scraper
Team Roster
| Agent | Title | Tier | Domain |
|---|---|---|---|
| conductor | COO | C-Suite | All — receives every inquiry |
| cto | CTO | C-Suite | Technical architecture, platform decisions |
| cfo | CFO | C-Suite | Financial ops, budgets |
| cko | CKO | C-Suite | Knowledge management, skill governance, decay-metadata enforcement (inferred notes must carry confidence + last_verified frontmatter; weekly audit rejects non-conforming notes) |
| legal | General Counsel | C-Suite | Contracts, MSA, SOW, agreements |
| vp-engineering | VP Engineering | VP | Code quality, release mgmt, tech debt |
| chief-of-staff | Chief of Staff | Management | Morning briefing, dept status, MCP health |
| scrum-leader | Scrum Lead | Management | Sprint planning, velocity, backlog |
| secretary | Secretary | Management | Timeline tracking, legal coordination |
| hr | HR Director | Management | Agent lifecycle, hiring, performance |
| alignment-monitor | CKO Agent | Management | Skill routing audits, orphan prevention |
| builder | Engineer | Specialist | Production code, tests, config |
| designer | Designer | Specialist | UI components, design tokens |
| forge | Data Engineer | Specialist | Large data ops (10K+ records) |
| professor | Domain Expert | Specialist | Domain instruction and tutoring |
| guardian | QA Lead | Specialist | Pre-commit audits, quality gates, destructive-action approval gate (DESTRUCTIVE_ACTION_GATE: irreversible-local / irreversible-external / bulk-send actions require typed approval before execution) |
| janitor | Maintenance | Specialist | Cleanup, file org, stale removal |
| proposal-writer | Sales | Specialist | Proposals, presentations |
| scout | Pattern Scout | Support | Background pattern detection |
| planner | Task Planner | Support | Background task tracking |
| quick | Micro Agent | Support | Trivial queries, fast responses |
| scraper | Web Scraper | Support | Web extraction |
| simulator | Protocol Tester | Support | Routing-regression validation (COO→specialist correctness, skill-matcher file accuracy, agent-spawn format); runs on every skill-index.json change |
| mesh-wrapper | A2A Mesh | Specialist | Agent-to-agent delegation, INTERRUPT protocol (SOFT: finish current tool call / HARD: abort), subscription, cache, and persistent IMPACT (cross-agent memory) |
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.
- 9d ago First seen · 685 lines · 149 tokens per session scan A 8a7e26c9cf65
conductor is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 17d ago), licensed MIT. It adds 149 tokens to every session and 8,902 once invoked, about $0.0007 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-31.
Other agents, from other repositories
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
project-discovery
Use this agent when you need to audit project state, map affected modules, or verify assumptions before implementation. Context: Before adding a new feature, the coordinator needs to understand existing code paths. user: "Audit the auth flow" assistant: "I'll use the project-discovery agent to map auth modules and…
technical-writer
Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…