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 X-School-Academy/skill-pilot --skill dev-swarm-stage-prdgit clone --depth 1 https://github.com/X-School-Academy/skill-pilotWrote 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/x-school-academy/skill-pilot/dev-swarm-stage-prd)<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/dev-swarm-stage-prd"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-stage-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/x-school-academy/skill-pilot/dev-swarm-stage-prd"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-stage-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.00049 | $0.01140 |
| Opus 5.5 | $0.00020 | $0.00456 |
| Sonnet 5.5 | $0.00010 | $0.00228 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
dev-swarm-stage-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 16d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage 05 - PRD (Product Requirements Document)
Create a comprehensive Product Requirements Document that defines the complete product behavior, including functional requirements, non-functional requirements, user flows, acceptance criteria, and all specifications needed to guide development.
When to Use This Skill
- User asks to start stage 05 (prd)
- User wants to define product requirements or acceptance criteria
- User asks about functional or non-functional requirements
Your Roles in This Skill
See dev-swarm/docs/general-dev-stage-rule.md for role selection guidance.
Role Communication
See dev-swarm/docs/general-dev-stage-rule.md for the required role announcement format.
Pre-Stage Check
Before starting, verify previous stages:
- Check if
00-init-ideas/through04-tech-research/folders have content (not just.gitkeep) - If any previous stage is empty and has no
SKIP.md:- Ask user: "Stage {XX} is not complete. Would you like to skip it or start from that stage first?"
Instructions
Step 1: Context Review
Read all files to understand the project:
ideas.md00-init-ideas/*.mdthrough04-tech-research/*.md- All markdown files
Step 2: Create Stage Proposal
General Rules: See dev-swarm/docs/general-dev-stage-rule.md → "Create Stage Proposal Rules" section.
If this stage is skipped (has SKIP.md), execute the next non-skipped stage's agent skill. Otherwise, create the file 05-prd/README.md with the following content:
2.1 Stage Goal
Brief the goal in 2-3 paragraphs:
- What this stage aims to achieve
- Why a comprehensive PRD is critical for successful development
- How this builds upon previous stages
- What deliverables will be produced
2.2 File Selection
Select files from these options based on project needs:
Core Requirements:
functional-requirements.md- Detailed functional requirements describing what the system must donon-functional-requirements.md- Performance, security, scalability, and other quality attributes
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.
- 16d ago First seen · 145 lines · 49 tokens per session scan A ee789cd576a9
dev-swarm-stage-prd is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,140 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-10-02.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
remove
Remove a deployed framework or addon from the current workspace.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…