A session guide for coding work in a Git repository, the folder used to track code changes. It classifies the task, records its phases, routes it through required skills, and applies review and completion checks.

Use it when implementing, fixing, debugging, refactoring, documenting, investigating, or resuming a coding session.

It gives coding tasks a recorded process so work is not casually started, committed, or closed without the required checks.

conductor — Skill for Claude Code by foundry-studio-lab

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add foundry-studio-lab/nzshrimper-senior-dev

Claude Code

/plugin install senior-dev

Made for: Claude Code.

Or install senior-dev, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 3 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/foundry-studio-lab/nzshrimper-senior-dev/conductor/github.svg)](https://agentmods.dev/skills/foundry-studio-lab/nzshrimper-senior-dev/conductor)

Your own site

<a href="https://agentmods.dev/skills/foundry-studio-lab/nzshrimper-senior-dev/conductor"><img src="https://agentmods.dev/badge/skills/foundry-studio-lab/nzshrimper-senior-dev/conductor/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/foundry-studio-lab/nzshrimper-senior-dev/conductor"><img src="https://agentmods.dev/badge/skills/foundry-studio-lab/nzshrimper-senior-dev/conductor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 155 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,093 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.

Model	Per session	Once invoked
Fable 5.1	$0.00155	$0.04093
Opus 5	$0.00077	$0.02047
Sonnet 5	$0.00031	$0.00819
Haiku 4.5	$0.00015	$0.00409

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

Security

Grade A, and why

conductor 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/SKILL.md · 295 lines

How it starts

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

senior-dev conductor

You are running a senior-dev session. You do not write code casually: every task goes through classification, the mandatory skill chain, recorded phases, review gates, and a clean close. The state CLI is the only way you record progress — never hand-edit .senior-dev/state.json, never claim a phase is done without recording it at that moment.

State CLI (all commands run from inside the target repo):

node "${CLAUDE_PLUGIN_ROOT}/scripts/state-cli.mjs" <subcommand> [flags]

1. Engage

Run node <plugin>/scripts/state-cli.mjs status (the session bootstrap gives the exact path). If it reports an active session, resume at the reported phase — its skill source and guard answer are already recorded, so skip the rest of §1; do not restart completed phases.
Skill source (fresh run only, before classifying). Decide which skills fill the process phases this run. Run node <plugin>/scripts/state-cli.mjs skills-config show.
- Config present: state its source as the project default and ask a one-beat confirm — "Project default: (with this repo's <mapped phases>). Use it, or choose another?" A bare "yes"/"use it" proceeds; naming another source switches.
- No config: ask the four-way question, superpowers marked default:
  1. own — this project's own skills fill each phase.
  2. superpowers (default) — the canonical chain.
  3. combo — superpowers base, this project's skills layered on where they exist.
  4. suggest — search for skills with find-skills and pick.
- Record the operator's answer for next time: state-cli skills-config set --source <s> [--steps 'plan=<skill>,review=<skill>'], and on first creation ask once: keep this config private (default) or share it with the team? On "share" run state-cli skills-config share and tell them to git add .senior-dev/skills.json.
- Record the run's choice once the session exists (after init): state-cli skill-source --source <s> --map '<phase→skill json>' [--suggestions '<json array of candidates the operator took>'] (add --suggestions when the source is suggest).
Universal guard (fresh run only, once per repo). Run state-cli guard status.
- absent and no recorded answer: ask once — "Install the universal enforcement hooks? They make the gates hold in Cowork, Codex, and plain terminals too — written to this repo's git hooks; existing hooks are preserved and chained." Yes → state-cli guard install. No → run state-cli guard uninstall (records the decline; safe no-op when nothing is installed); never re-ask.
- installed: proceed silently. stale: run state-cli guard install again (silent refresh; consent already given).
- absent but the config says installed (hooks went missing): mention it once and re-offer (tell them apart via the guard key in step 2's skills-config show output — guard status prints bare absent in both cases).
- declined: stay silent; /senior-dev:guard remains available.
Classify the task as exactly one of the types below. If genuinely ambiguous, ask the operator ONE multiple-choice question.
Initialise: state-cli init --task "<one-line task>" --type <type>

Read the full file on GitHub · 295 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/skill-sources.md 1.9 KB

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.

10d ago First seen · 295 lines · 155 tokens per session scan A 5034839a414b

Subscribe to this mod's changes

conductor is a skill published in the GitHub repository foundry-studio-lab/nzshrimper-senior-dev (4 stars, last pushed 2mo ago), licensed MIT. It adds 155 tokens to every session and 4,093 once invoked, about $0.0008 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-31.

Claude Code Git and workflow Planning ai claude claude-code-plugin developer-tools

procoder

Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…

azrtydxb/procoder · 101 tokens

pr-feedback

Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.

jjanczur/tyran · 57 tokens

detect-task

Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.

restarter/lets-workflow · 41 tokens

loop-bb-pr

A command that prepares a repeating check for a Bitbucket pull request. A pull request is a request to review and merge code changes into a project.

restarter/lets-workflow · 118 tokens

take-task

A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.

restarter/lets-workflow · 76 tokens

session-boundary

Internal skill for commands. Resolve and VALIDATE this branch's session boundary - the ref a session's commit range is measured from - and report how much it can be trusted. Do not trigger on user conversation; only when a command needs the session range.

restarter/lets-workflow · 55 tokens