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 FortiumPartners/ensemble --skill ensemble-full-create-prdgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/ensemble-full-create-prd)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-full-create-prd"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-full-create-prd.svg" alt="Measured on agentmods" 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.00077 | $0.03174 |
| Opus 5 | $0.00039 | $0.01587 |
| Sonnet 5 | $0.00015 | $0.00635 |
| Haiku 4.5 | $0.00008 | $0.00317 |
Grade A, and why
ensemble-full-create-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 5d 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.
This is a copy
86% identical to ensemble-create-prd — 347 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ensemble:create-prd
Mission: Create a comprehensive Product Requirements Document (PRD) through structured elicitation, contextual research, and adversarial self-review. Adapts depth to project scale (solo dev through enterprise). Uses clarifying interviews and creative elicitation techniques to surface hidden requirements before writing. Every PRD passes an Implementation Readiness Gate before being saved to ensure handoff quality.
Constraints:
- DO NOT implement, build, or execute any work described in the product description
- This command creates ONLY a PRD document
- The arguments describe what should be documented, not what should be built
- After creating the PRD, stop and wait for user approval before any implementation
- DO NOT skip the elicitation phase -- always ask clarifying questions before generating requirements
- DO NOT save the PRD until it passes the Implementation Readiness Gate
- Mark every unresolved ambiguity inline with [NEEDS CLARIFICATION: ] rather than making a best-guess assumption — these markers drive the refine-prd interview
Phase 1: Structured Elicitation
Step 1: Scale Detection
Determine project complexity to calibrate PRD depth
Actions:
- Ask the user: 'Is this a solo/side project, small team (2-5), or enterprise/multi-team effort?'
- If user provided a product description as arguments, read it first, then ask -- don't make them repeat themselves
- Set depth level: LIGHT (solo -- 5-10 requirements, minimal ceremony), STANDARD (small team -- 10-25 requirements, full ACs), DEEP (enterprise -- 25+ requirements, risk analysis, compliance section)
- Announce the chosen depth level so the user can override if needed
Step 2: Problem Space Interview
Gather core product context through a one-question-at-a-time interview
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.
- 5d ago First seen · 254 lines · 77 tokens per session scan A dcc154c503db
ensemble-full-create-prd is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 3,174 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to ensemble-create-prd, differing in 347 lines, and is treated as a copy.
Other skills, from other repositories
context-recovery
Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Use when the user asks what happened in prior project/PR/branch/file/error work, needs a handoff brief, wants old decisions or validations recovered, or asks to summarize cross-session project activity…
overleaf
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
dev
This skill should be used when the user asks to start, restart, keep alive, or inspect the local pikiclaw development service, including npm run dev, local debug bot startup, dashboard verification, and dev log checks.
bmad-quick-dev-new-preview
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
bmad-create-story
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".
bmad-quick-dev
Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]".