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-statusgit 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-status)<a href="https://agentmods.dev/skills/vasilistsavalias/conductor_for_codex/conductor-status"><img src="https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-status.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00815 |
| Opus 5 | $0.00007 | $0.00407 |
| Sonnet 5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
conductor-status 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 — 99 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. This command is read-only — it does not modify any files.
1.0 SYSTEM DIRECTIVE
You are an autonomous AI agent providing a status overview of the Conductor project. Read the tracks registry and all plan files, then output a structured summary. Do not modify any files. Do not stop for user confirmation.
1.1 SETUP CHECK
Universal File Resolution Protocol: Check conductor/<file> first; if missing, read conductor/index.md for canonical paths.
Check for:
conductor/tracks.md(Tracks Registry)conductor/product.mdconductor/tech-stack.mdconductor/workflow.md
If any required file is missing: output a warning listing the missing files and suggest "Run /conductor-setup to initialize.", then continue with whatever data is available (do not halt completely — partial status is better than nothing).
2.0 STATUS OVERVIEW PROTOCOL
2.1 Read the Tracks Registry
-
Read
conductor/tracks.md. -
Parse all track sections. A track section is delimited by
---. For each section, extract:- Status:
[ ](new),[~](in_progress),[x](implemented — pending review) - Track description (from
**Track: ...**line) - Track folder link
- Status:
-
For each track, read its
plan.mdvia the track'sindex.md. Parse tasks:- Count total tasks: lines matching
- [ ] Task:,- [~] Task:,- [x] Task: - Count completed tasks:
- [x] Task: - Identify current in-progress task:
- [~] Task:(if any) - Identify next pending task: first
- [ ] Task:(if any) - Identify blockers: tasks or lines explicitly labeled "BLOCKED" or "BLOCKER"
- Count total tasks: lines matching
2.2 Generate and Output Status Report
Output the following format:
═══════════════════════════════════════
CONDUCTOR STATUS REPORT
<current date and time>
═══════════════════════════════════════
PROJECT: <product name from conductor/product.md>
TRACKS SUMMARY
Total tracks: <N>
New (not started): <N>
In progress: <N>
Implemented: <N> ← pending review
Archived: (not tracked here — check conductor/archive/)
─────────────────────────────────────
<For each track, in registry order:>
[<status icon>] Track: <description>
ID: <track_id>
Progress: <completed>/<total> tasks (<percent>%)
Current: <current in-progress task, or "—">
Next: <next pending task, or "All done — run /conductor-review">
Blockers: <blocker text, or "None">
─────────────────────────────────────
OVERALL PROGRESS: <total_completed>/<total_tasks> tasks (<percent>%)
STATUS: <On Track | In Progress | Blocked | All Implemented>
═══════════════════════════════════════
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 · 99 lines · 14 tokens per session scan A a9613fef757a
conductor-status is a skill published in the GitHub repository vasilistsavalias/conductor_for_codex (20 stars, last pushed 19d ago), licensed Apache-2.0. It adds 14 tokens to every session and 815 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.
Other skills, from other repositories
task
\ You are executing a task within the LobeHub task system. Use the lh task CLI via runCommand to manage your task and related resources.
duduclaw-platform
Use the DuDuClaw MCP tools (persistent memory, shared wiki, task board, channel messaging) when the user asks to remember something across sessions, share knowledge with their team's AI employees, manage tasks, or message someone on LINE/Telegram/Discord/Slack. Requires a running DuDuClaw gateway (npx duduclaw onboard…
duduclaw
Use DuDuClaw — a self-hosted AI-employee platform — for cross-session memory, team-shared wiki knowledge, task boards, and messaging humans over LINE/Telegram/Discord/Slack. Applies when the user mentions DuDuClaw, asks their agent to remember things durably, or wants to reach people on messaging channels from an…
kickoff-prep
Prepares the onboarding kickoff — agenda, stakeholder map, success criteria to confirm, and a proposed milestone plan. Use before a kickoff call with a new customer or when asked to "prep the kickoff for X".
post-call-followup
Turns the most recent customer call into structured follow-up — action items with owners, commitments made, risks heard, and a draft recap message. Use after a customer call ends, or when the user says "summarize my call with X" or "draft the follow-up for X".
gh-issues
Walk over all open GitHub issues that are unassigned or assigned to the current user, and process each one via the gh-issue skill, sequentially.