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 produckyou-design/agent-director-protocol --skill agent-directorgit clone --depth 1 https://github.com/produckyou-design/agent-director-protocolWrote 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/produckyou-design/agent-director-protocol/agent-director)<a href="https://agentmods.dev/skills/produckyou-design/agent-director-protocol/agent-director"><img src="https://agentmods.dev/badge/skills/produckyou-design/agent-director-protocol/agent-director/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/produckyou-design/agent-director-protocol/agent-director"><img src="https://agentmods.dev/badge/skills/produckyou-design/agent-director-protocol/agent-director.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00056 | $0.06875 |
| Opus 5 | $0.00028 | $0.03438 |
| Sonnet 5 | $0.00011 | $0.01375 |
| Haiku 4.5 | $0.00006 | $0.00688 |
Grade A, and why
agent-director 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.
How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Director (Claude Code adapter)
This skill binds the platform-neutral agent-director-protocol to Claude Code's
mechanics. It does not restate the full protocol — the authoritative rules
live in core/. Read the relevant core doc before acting
on any section below.
Roles, mapped to Claude Code
- Director — the main conversation model (this session). Plans, decomposes, delegates, and reviews. Never writes product code itself except after a recorded takeover (see below) — and the same rule covers running state-changing operations (deploys, migrations, release pipelines), which are delegated like any other work. Read-only inspection is fine; it is part of reviewing.
- Implementer — a subagent spawned with the Task/Agent tool. Its model is
selected by the active adapter profile and recorded explicitly in the Task
Contract; the profile under
../../profiles/provides the current default (see alsoCLAUDE.md.examplefor how a project points at one). - Reviewer — the director itself, unless a profile sets
reviewer.inheritto something else. Full rule:ROLE-CONTRACT.md.
Worker-mode boundary (mandatory)
A task tree has exactly one Director: the root/current parent session. Every
spawned subagent is a worker or reviewer according to its assigned role. The
spawned subagent is never a Director under any circumstance; only the
root/current parent session is Director. The role name must be assigned before
creation, and director is not a valid worker role.
parent Director's Task Contract is authoritative. A worker executes only its
assigned mission and reports evidence or status to that parent. It MUST NOT
announce director_mode: on, publish a root-level task_start or composition
disclosure, rewrite or re-decompose the parent contract, spawn or manage
workers, integrate or merge work, or declare the overall task complete.
What ships with it
7 files 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.
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 · 436 lines · 56 tokens per session scan A c585f5f0b0cb
agent-director is a skill published in the GitHub repository produckyou-design/agent-director-protocol (5 stars, last pushed 27d ago), licensed MIT. It adds 56 tokens to every session and 6,875 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…