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 rbarcante/claude-conductor --skill conductor-methodologygit clone --depth 1 https://github.com/rbarcante/claude-conductorWrote 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/rbarcante/claude-conductor/conductor-methodology)<a href="https://agentmods.dev/skills/rbarcante/claude-conductor/conductor-methodology"><img src="https://agentmods.dev/badge/skills/rbarcante/claude-conductor/conductor-methodology/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/skills/rbarcante/claude-conductor/conductor-methodology"><img src="https://agentmods.dev/badge/skills/rbarcante/claude-conductor/conductor-methodology.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.00052 | $0.02351 |
| Opus 5 | $0.00026 | $0.01175 |
| Sonnet 5 | $0.00010 | $0.00470 |
| Haiku 4.5 | $0.00005 | $0.00235 |
Grade A, and why
conductor-methodology 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor Methodology Skill
Conductor is a context-driven development framework that structures software development through a rigorous lifecycle: Context → Spec & Plan → Implement. This skill provides guidance on Conductor's principles, file structures, and workflows.
Core Philosophy
Measure twice, code once. Conductor treats context as a managed artifact alongside code, transforming repositories into a single source of truth that drives every agent interaction with deep, persistent project awareness.
Key Principles
- Plan before you build: Create specs and plans that guide implementation
- Maintain context: Ensure AI follows style guides, tech stack choices, and product goals
- Iterate safely: Review plans before code is written
- Work as a team: Set project-level context shared across the team
Project Structure
Core Context Files (conductor/)
Located in the conductor/ directory at project root:
product.md: Product vision, users, goals, and featuresproduct-guidelines.md: Prose style, brand messaging, visual identitytech-stack.md: Technology choices, languages, frameworks, databasesworkflow.md: Development workflow (TDD, commit strategy, coverage requirements)code_styleguides/: Language-specific coding standardstracks.md: Master list of all tracks with status and links
Track Structure (conductor/tracks/)
Each track lives in conductor/tracks/<track_id>/:
spec.md: Detailed requirements for the trackplan.md: Hierarchical plan with phases, tasks, and sub-tasksdecisions.md: Architecture Decision Records for track decisionsreview.md: Auto-generated code review report on track completionmetadata.json: Track metadata (ID, type, status, timestamps)
Track Lifecycle
Tracks represent high-level units of work (features, bugs, chores):
- Creation (
/conductor:newTrack): Generate spec and plan - In Progress: Mark as
[~]when work begins - Completed: Mark as
[x]when all tasks finish - Cleanup: Archive or delete completed tracks
What ships with it
2 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.
- 9d ago First seen · 285 lines · 52 tokens per session scan A 5fec299109a6
conductor-methodology is a skill published in the GitHub repository rbarcante/claude-conductor (56 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 2,351 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.