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-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-create-prd)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-create-prd"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-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.00029 | $0.03168 |
| Opus 5 | $0.00015 | $0.01584 |
| Sonnet 5 | $0.00006 | $0.00634 |
| Haiku 4.5 | $0.00003 | $0.00317 |
Grade A, and why
ensemble-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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ensemble-full-create-prd — 86% identical, 347 lines differ
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:create-prd
This Codex skill mirrors the Ensemble slash command /ensemble:create-prd.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
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.
Workflow
Phase 1: Structured Elicitation
1. Scale Detection Determine project complexity to calibrate PRD depth
- 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
2. Problem Space Interview Gather core product context through a one-question-at-a-time interview
- INTERVIEW PROTOCOL: Ask exactly ONE question, wait for the user's full answer, then ask the next. Never batch questions.
- Determine which of these questions are NOT already answered by the product description provided as arguments, then ask only the unanswered ones in order:
- Q1: 'What problem does this solve, and who feels the pain today?'
- Q2: 'Who are the primary users? (describe by role, not by name)'
- Q3: 'What does success look like -- ideally with specific metrics?'
- Q4: 'What constraints apply? (budget, timeline, tech stack, compliance, etc.)'
- Q5: 'What existing solutions have been tried or considered, and why weren't they enough?'
- After each answer: acknowledge it briefly (1 sentence), then ask the next question
- After the final answer: summarize what you heard in 3-4 sentences and ask the user to confirm before continuing
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.
- 6d ago First seen · 241 lines · 29 tokens per session scan A c08c3bfbe194
ensemble-create-prd is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 3,168 once invoked, about $0.0001 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-30.
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]".