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 vasilistsavalias/conductor_for_codex --skill conductor-implementgit clone --depth 1 https://github.com/vasilistsavalias/conductor_for_codexWrote 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/vasilistsavalias/conductor_for_codex/conductor-implement)<a href="https://agentmods.dev/skills/vasilistsavalias/conductor_for_codex/conductor-implement"><img src="https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-implement/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/vasilistsavalias/conductor_for_codex/conductor-implement"><img src="https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Agent Snooping · line 88 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00023 | $0.01597 |
| Opus 5.5 | $0.00009 | $0.00639 |
| Sonnet 5.5 | $0.00005 | $0.00319 |
| Haiku 4.5 | $0.00002 | $0.00160 |
Grade A, and why
conductor-implement 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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
CRITICAL: Conductor artifacts are local-only.
- You MUST NOT modify anything outside the repository root.
- Ensure
.gitignoreincludesconductor/. If missing, add it. - You MUST NOT
git add/git commitConductor artifacts unless implementing tasks that explicitly require it.
1.0 SYSTEM DIRECTIVE
You are an autonomous AI agent executing tracks in the Conductor spec-driven development framework. Operate independently. Do not stop to ask for confirmation unless you encounter an unrecoverable error or a genuine high-impact ambiguity that cannot be resolved from available context. Announce your decisions as you make them.
If any file operation or shell command fails, halt immediately, report the specific failure, and wait for instructions.
1.1 SETUP CHECK
Verify the Conductor environment before proceeding.
-
Check for the existence of these files using the Universal File Resolution Protocol (see below):
- Product Definition (
conductor/product.md) - Tech Stack (
conductor/tech-stack.md) - Workflow (
conductor/workflow.md) - Tracks Registry (
conductor/tracks.md)
- Product Definition (
-
Universal File Resolution Protocol: Resolve each file by checking in this order:
conductor/<file>(default location)conductor/index.md→ read it to find the canonical path
-
If any required file is missing: report which file is missing, announce "Conductor is not set up. Please run
/conductor-setupfirst.", and halt.
2.0 TRACK SELECTION
Identify the track to implement without requiring user confirmation.
-
Resolve Tracks Registry using the Universal File Resolution Protocol.
-
Parse the registry: Split on
---separators. For each section extract:- Status:
[ ](new),[~](in_progress),[x](implemented) - Track description (from
**Track: ...**line) - Link to track folder
- Status:
-
Select track:
- If
$ARGUMENTSis provided: find the first track whose description contains the argument text (case-insensitive). If no match found, report "No track matching '$ARGUMENTS' found." and list available tracks, then halt. - If
$ARGUMENTSis empty: select the first track with status[ ]or[~](resume in-progress first, then start the next new one). - If no eligible track found: announce "No incomplete tracks found. All tracks are implemented or the registry is empty." and halt.
- If
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.
- 1mo ago First seen · 146 lines · 23 tokens per session scan A a946da8f9431
conductor-implement is a skill published in the GitHub repository vasilistsavalias/conductor_for_codex (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,597 once invoked, about $0.0001 per session on Opus 5.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
prisma-postgres-setup
Set up a new Prisma Postgres database and connect it to a local project using the Management API. Use when asked to "set up a database", "create a Prisma Postgres project", "get a connection string", "connect my app to Prisma Postgres", or "provision a database".
prisma-client-api
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".
pake
Package a website or local web build as a desktop app with Pake. Use for packaging, CLI options, icons, bundle identifiers, or WebView proxy setup. Not for unrelated Tauri development or uninstalling apps.
prisma-mongodb-upgrade
Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma Next. Triggers on "upgrade prisma mongodb"…
handoff
Write or resume a session handoff between AI tools.