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 jstoup111/ai-conductor --skill prdgit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/jstoup111/ai-conductor/prd)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/prd"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/prd/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/jstoup111/ai-conductor/prd"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/prd.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.00043 | $0.01446 |
| Opus 5.5 | $0.00017 | $0.00578 |
| Sonnet 5.5 | $0.00009 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
prd 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 13d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Author the product requirements document for a product-track feature: the what and why,
enumerated as testable functional requirements that stories extract from directly. Runs only when
/explore set Track: product; technical-track features skip this step entirely.
Correctness gate: functional requirements are load-bearing — stories extract from them directly.
Apply the /verify-claims protocol before locking FRs: any FR resting on an assumption about user
need, scope, or existing behavior must be flagged with its confidence and HARD-BLOCKED for operator
approval (or HALTed if autonomous) — never lock an FR on an unconfirmed assumption.
Boundaries
prd produces a single artifact — a design doc in .docs/specs/ — and nothing else.
Do NOT:
- Write code, migrations, configs, tests, stubs, plans, or stories
- Create files outside
.docs/specs/ - Invoke
/plan,/stories, or any other skill
Product-only — the hard rule
A PRD states goals and requirements. It MUST NOT name the new internal mechanism by which this feature is built. These are leaks no matter how convenient:
- command names, subcommands, or CLI flags
- file paths, directory layouts, config-file names, or config keys
- function / class / module / type names, signatures, or pseudocode
- the library / protocol / service / mechanism chosen for this feature (e.g. "via an MCP server", "a symlink", "SQLite", "a post-checkout hook", a named algorithm)
- data schemas, table/column names, wire formats, ports
Name the capability or behavior ("the operator can adopt a platform in one action"), never the mechanism. Carve-out: a pre-existing external constraint or dependency the feature must live within (an existing API it must call, "must run offline", a mandated datastore) MAY be named as a requirement under Dependencies or Non-Functional Requirements — that is product reality, not a leaked internal mechanism. The distinction: choosing a new internal mechanism = leak; stating an external constraint we don't control = requirement.
What ships with it
2 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.
- 13d ago Changed · +1 lines 54b7f6ebcaf6
- 27d ago Changed · +3 lines 824a540fdf60
- 2mo ago First seen · 120 lines · 43 tokens per session scan A c6ee48e30479
prd is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 1,446 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.