agentmods.dev

conductor-review

conductor-review is a skill for Claude Code from vasilistsavalias/conductor_for_codex. It costs 28 tokens per session (1,702 once invoked), scanned A, original, Apache-2.0.

A quality-check step for the Conductor development framework, which organizes coding work into planned tracks. It compares a completed track with its plan and rules.

In plain words
What is it for?
Reviewing completed development tracks, checking for critical or high-priority problems, applying straightforward fixes, and archiving or restarting the track.
Why use it?
It gives the work a clear pass-or-fail checkpoint. It also handles failed tracks by removing and restarting them, while applying simple fixes for medium or low issues.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Codex.

not rated 20repo 21d ago A scan SkillSpector: pass 28 tokens original Apache-2.0

Good fit Reviewing completed development tracks, checking for critical or high-priority problems, applying straightforward fixes, and archiving or restarting the track.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vasilistsavalias/conductor_for_codex/conductor-review
View source ↗ vasilistsavalias/conductor_for_codex
Install

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.

Any agent
npx skills add vasilistsavalias/conductor_for_codex --skill conductor-review
Clone the repo
git clone --depth 1 https://github.com/vasilistsavalias/conductor_for_codex

Made for: Claude Code.

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-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-review/github.svg)](https://agentmods.dev/skills/vasilistsavalias/conductor_for_codex/conductor-review)
Your own site
<a href="https://agentmods.dev/skills/vasilistsavalias/conductor_for_codex/conductor-review"><img src="https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-review/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.

agentmods 80×15 button for conductor-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/vasilistsavalias/conductor_for_codex/conductor-review"><img src="https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,702 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00028 $0.01702
Opus 5 $0.00014 $0.00851
Sonnet 5 $0.00006 $0.00340
Haiku 4.5 $0.00003 $0.00170

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

Security

Grade A, and why

conductor-review 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 10d 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.

skills/conductor-review/SKILL.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 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 .gitignore includes conductor/. If missing, add it.

1.0 SYSTEM DIRECTIVE

You are an autonomous AI agent acting as a Principal Software Engineer and Code Review Architect in the Conductor framework. Your role is a strict quality gate.

  • PASS (no Critical/High issues): auto-archive the track, no user input needed.
  • FAIL (Critical or High issues found): delete the track, then immediately start a new one.
  • MEDIUM/LOW issues only: auto-apply simple fixes, re-run checks. If clean after fixes → archive. If not → treat as FAIL.

Operate autonomously. Do not pause to ask the user for decisions during the review process. Announce your findings and actions as you go.

If invoked directly by the user (not from conductor-implement), proceed exactly the same way.

1.1 SETUP CHECK

Verify using the Universal File Resolution Protocol:

Universal File Resolution Protocol: For each required file, check conductor/<file> first; if missing, read conductor/index.md to find the canonical path.

Required files:

  • conductor/tracks.md (Tracks Registry)
  • conductor/product.md
  • conductor/tech-stack.md
  • conductor/workflow.md
  • conductor/product-guidelines.md

If any are missing: report which files are missing, announce "Conductor is not set up. Run /conductor-setup first.", and halt.

2.0 IDENTIFY REVIEW TARGET

  1. If $ARGUMENTS is provided: use it as the track ID or description to find the target track.
  2. If called from conductor-implement: the <track_id> is already in scope — use it directly.
  3. If neither: read conductor/tracks.md and find the first track with status [x] (implemented, pending review). If no [x] track exists, check for [~] tracks and use the first one. If nothing found, announce "No implemented tracks found to review." and halt.

Read the full file on GitHub · 170 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. 10d ago First seen · 170 lines · 28 tokens per session scan A 47362ffbaa4b

Subscribe to this mod's changes

conductor-review is a skill published in the GitHub repository vasilistsavalias/conductor_for_codex (20 stars, last pushed 21d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,702 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.

Code reviewProject managementagentic-aichatgptcodexconductorcontext-driven-developmentgemini
Related

Other skills, from other repositories

pr-review-triage

Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.

cobusgreyling/loop-engineering · 35 tokens

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.

lobehub/lobehub · 0 tokens

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…

zhixuli0406/DuDuClaw · 81 tokens

doc-gather

Use when you need to gather context for a Jira ticket or PR. Resolves ticket metadata, clones relevant repos, collects candidate files, runs filtering pipeline, and produces workspace/context-package.json.

opendatahub-io/ai-helpers · 42 tokens

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…

zhixuli0406/DuDuClaw · 77 tokens

ship-pr

Ship one pull request, monitor hosted CI and review feedback, follow PR policy, and request authorization before merging and cleaning up.

conn-castle/agent-layer · 28 tokens