Conductor-for-all: Skill for Claude Code

.agents/skills/conductor-setup/SKILL.md

conductor-setup is a skill for Claude Code, Codex from hlhr202/Conductor-for-all. It costs 17 tokens per session (9,159 once invoked), scanned A, original, Apache-2.0.

A setup guide for Conductor, a project-management method for software work, that creates the project files and environment it needs.

In plain words
What is it for?
It helps initialize a Conductor project and configure its working environment.
Why use it?
It removes the guesswork from preparing a project before using Conductor.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is hlhr202/Conductor-for-all's own configuration. It tells Claude Code and Codex how to work on Conductor-for-all itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Conductor-for-all configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is - [Code Style Guides](./code_styleguides/).

Reuse

Borrowing it

Nothing to install: this file belongs to hlhr202/Conductor-for-all. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hlhr202/Conductor-for-all/main/.agents/skills/conductor-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hlhr202/Conductor-for-all

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for conductor-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/hlhr202/conductor-for-all/conductor-setup.svg)](https://agentmods.dev/skills/hlhr202/conductor-for-all/conductor-setup)
Your own site
<a href="https://agentmods.dev/skills/hlhr202/conductor-for-all/conductor-setup"><img src="https://agentmods.dev/badge/skills/hlhr202/conductor-for-all/conductor-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.09159
Opus 5 $0.00009 $0.04580
Sonnet 5 $0.00003 $0.01832
Haiku 4.5 $0.00002 $0.00916

Measured 8d ago against content hash e4b2a77c7756, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

.agents/skills/conductor-setup/SKILL.md · 535 lines

How it starts

The opening of the file, as written. The whole thing — 535 lines — stays where its author put it; the contents beside it link to each section on GitHub.

1.0 SYSTEM DIRECTIVE

You are an AI agent. Your primary function is to set up and manage a software project using the Conductor methodology. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions.

CRITICAL: You must validate the success of every tool call. If a tool call fails (e.g., due to a policy restriction or path error), you should attempt to intelligently self-correct by reviewing the error message. If the failure is unrecoverable after a self-correction attempt, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.

PLAN MODE PROTOCOL: This setup process runs entirely within Plan Mode. While in Plan Mode, you are explicitly permitted and required to use write_file, replace, and authorized run_shell_command calls to create and modify files within the conductor/ directory. CRITICAL: You MUST use relative paths starting with conductor/ (e.g., conductor/product.md) for all file operations. Do NOT use absolute paths, as they will be blocked by Plan Mode security policies. REDIRECTION (e.g., > or >>) is strictly NOT allowed in run_shell_command calls while in Plan Mode and will cause tool failure. Do not defer these actions to a final execution phase; execute them immediately as each step is completed and approved by the user.

1.1 PRE-INITIALIZATION OVERVIEW

  1. Provide High-Level Overview:
    • Present the following overview of the initialization process to the user:

      "Welcome to Conductor. I will guide you through the following steps to set up your project:

      1. Project Discovery: Analyze the current directory to determine if this is a new or existing project.
      2. Product Definition: Collaboratively define the product's vision, design guidelines, and technology stack.
      3. Configuration: Select appropriate code style guides and customize your development workflow.
      4. Track Generation: Define the initial track (a high-level unit of work like a feature or bug fix) and automatically generate a detailed plan to start development.

      Let's get started!"

Read the full file on GitHub · 535 lines

Changes

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.

  1. 8d ago First seen · 535 lines · 17 tokens per session scan A e4b2a77c7756

Subscribe to this mod's changes

conductor-setup is a skill published in the GitHub repository hlhr202/Conductor-for-all (52 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 9,159 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

jira-assistant

Manage Jira issues via Atlassian MCP — search, create, update, transition status, and handle sprint tasks. Auto-detects workspace configuration. Use when user says "create a Jira ticket", "update my sprint", "check Jira status", "transition this issue", "search Jira", or "move ticket to done". Do NOT use for…

tech-leads-club/agent-skills · 84 tokens

nx-generate

Generate code using Nx generators — scaffold projects, libraries, features, or run workspace-specific generators with proper discovery, validation, and verification. Use when user says "create a new library", "scaffold a component", "generate code with Nx", "run a generator", "nx generate", or any code scaffolding…

tech-leads-club/agent-skills · 110 tokens

nx-workspace

Configure, explore, and optimize Nx monorepo workspaces. Use when setting up Nx, exploring workspace structure, configuring project boundaries, analyzing affected projects, optimizing build caching, or implementing CI/CD with affected commands. Keywords — nx, monorepo, workspace, projects, targets, affected. Do NOT…

tech-leads-club/agent-skills · 87 tokens

sdd-tasks

Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.

Gentleman-Programming/gentle-ai · 25 tokens

issue-creation

Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.

Gentleman-Programming/gentle-ai · 30 tokens

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens