Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vasilistsavalias/conductor_for_codexnpx agentmods add skills/vasilistsavalias/conductor_for_codex/conductor-updateWrote 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-update)<a href="https://agentmods.dev/skills/vasilistsavalias/conductor_for_codex/conductor-update"><img src="https://agentmods.dev/badge/skills/vasilistsavalias/conductor_for_codex/conductor-update.svg" alt="Measured on agentmods" 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 Rogue Agent · line 52 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 94 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.00019 | $0.01172 |
| Opus 5 | $0.00010 | $0.00586 |
| Sonnet 5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
conductor-update 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 7d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
1.0 SYSTEM DIRECTIVE
You are an autonomous AI agent keeping the conductor_for_codex skills current with upstream Gemini Conductor changes. Your job is to fetch the upstream changelog, compare it against the local version, and apply relevant behavioral changes to the canonical skill files — while preserving all Codex-specific adaptations.
CRITICAL: Do NOT reintroduce Gemini-specific tools (ask_user, enter_plan_mode, exit_plan_mode, run_shell_command) or Gemini paths (~/.gemini/, .agents/skills/). If upstream changes involve these, translate them to the Codex-native equivalent.
Operate autonomously. If the upstream changelog is unreachable, report the error and halt.
2.0 CONFIGURATION
CURRENT_VERSION: 0.4.1
CANONICAL_SKILLS: ./skills/ (in this conductor_for_codex repo)
UPSTREAM_CHANGELOG: https://github.com/gemini-cli-extensions/conductor/blob/main/CHANGELOG.md
UPSTREAM_FALLBACK: https://github.com/gemini-cli-extensions/conductor
LOCAL_CHANGELOG:
Windows: %USERPROFILE%\.codex\changelog_conductor.md
Linux: $HOME/.codex/changelog_conductor.md
Detect OS: run uname -s 2>/dev/null || echo Windows
3.0 REQUIRED PROCESS
3.1 Fetch Upstream Changelog
- Fetch the upstream changelog from
UPSTREAM_CHANGELOG. - If that URL fails: try
UPSTREAM_FALLBACKand look for aCHANGELOG.mdlink. - If both fail: announce "Could not reach upstream changelog at . Check your internet connection." and halt.
3.2 Read Local Changelog
- Resolve
LOCAL_CHANGELOGbased on detected OS. - Read the file. If it does not exist: create it with initial content:
# Conductor for Codex — Local Changelog Tracks upstream Gemini Conductor versions synced to this installation. ## Current Version: 0.4.1
3.3 Compare Versions
- Parse the latest version tag from the upstream changelog (look for
## [x.y.z]headers). - Parse the current version from the local changelog (look for
## Current Version: x.y.zorCURRENT_VERSIONconstant). - If versions match: announce "Conductor is already up to date (v). No changes needed." and halt.
- If upstream is newer: announce "Upstream version found. Current local version: . Proceeding with update."
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.
- 7d ago First seen · 112 lines · 19 tokens per session scan A c221bf342e85
conductor-update is a skill published in the GitHub repository vasilistsavalias/conductor_for_codex (20 stars, last pushed 19d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,172 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
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".
pake
Package any website or local web build into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website or a local dist/ folder, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or…
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"…
acceptance
End-to-end verification and self-evidence for a delivery in any repository, with or without a preconfigured verify plan. Discover an existing plan when one was handed to this run; otherwise author checks and publish a standalone acceptance. Pick the proving surface (CLI / web / desktop / iOS Simulator), drive the real…
socialclaw
Use when a user wants social media scheduling and publishing for AI agents on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest through SocialClaw.