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-trd-foremangit 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-trd-foreman)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-create-trd-foreman"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-create-trd-foreman/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/fortiumpartners/ensemble/ensemble-create-trd-foreman"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-create-trd-foreman.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.00045 | $0.02547 |
| Opus 5 | $0.00023 | $0.01273 |
| Sonnet 5 | $0.00009 | $0.00509 |
| Haiku 4.5 | $0.00005 | $0.00255 |
Grade A, and why
ensemble-create-trd-foreman 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 9d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:create-trd-foreman
This Codex skill mirrors the Ensemble slash command /ensemble:create-trd-foreman.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Create a Foreman-native Technical Requirements Document (TRD) from a Product Requirements Document (PRD).
The resulting TRD must be machine-consumable by Foreman's existing parseTrd() parser and suitable for
immediate native task creation via foreman sling prd. Perform PRD validation, architecture design with
alternatives, and a structured task breakdown with deterministic markdown tables. All outputs are saved to docs/TRD/.
Workflow
Phase 1: PRD Ingestion and Validation
1. PRD Ingestion Parse and analyze existing PRD document from $ARGUMENTS path
- Read PRD file from specified path
- Validate document structure (required sections present)
- Extract key requirements with REQ-NNN IDs
- Build requirements registry for traceability tracking
2. Requirements Validation Ensure completeness of functional and non-functional requirements
- Validate all required sections present (Product Summary, User Analysis, Goals, Technical Requirements, Acceptance Criteria)
- Check acceptance criteria are testable and use Given/When/Then format
- Verify REQ-NNN format numbering is consistent and sequential
- Verify constraints and non-goals are documented
3. Acceptance Criteria Review Validate testable acceptance criteria from the PRD before TRD generation
- Ensure each requirement has measurable acceptance criteria with Given/When/Then items
- Verify AC-NNN-M sub-item format under each REQ-NNN
- Check that every Must requirement has at least 2 ACs (happy path + edge case)
- Do NOT validate TRD traceability here -- the TRD has not been generated yet
4. Implementation Readiness Gate Check Check if the PRD passed its own readiness gate before proceeding
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.
- 9d ago First seen · 221 lines · 45 tokens per session scan A 1957cbb811d7
ensemble-create-trd-foreman is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,547 once invoked, about $0.0002 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…
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.
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.
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-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
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]".