Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add FortiumPartners/ensemble/plugin install ensemble-codexWrote 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-workstream-trd)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-create-workstream-trd"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-create-workstream-trd.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.00033 | $0.00686 |
| Opus 5 | $0.00016 | $0.00343 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
ensemble-create-workstream-trd 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:create-workstream-trd
This Codex skill mirrors the Ensemble slash command /ensemble:create-workstream-trd.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Combine multiple canonical TRDs into one generated, executable workstream TRD that preserves source PRD/TRD/REQ/AC provenance and can be passed as the single input to /ensemble:implement-trd-beads.
Source TRDs remain canonical. The generated workstream TRD is an execution artifact that normalizes the graph-critical Master Task List while preserving source task markdown verbatim. It decomposes every referenced PRD acceptance criterion into AC-level implementation, executable-test, and validation tasks with Definition of Done evidence requirements. Generated workstream files use micro UUID document IDs (TRD-YYYY-<8hex>-workstream-.md), not sequence numbers, to avoid collisions across large teams.
Workflow
Phase 1: Generate Workstream TRD
1. Parse Arguments Validate source TRD paths and locate deterministic TRD CLI
- Extract all .md paths from $ARGUMENTS in the order provided. Require at least two TRD paths.
- If fewer than two paths are supplied: print 'ERROR: create-workstream-trd requires two or more TRD paths.' and HALT.
- Resolve TRD_CLI to first existing path among: ${CLAUDE_PLUGIN_ROOT}/lib/trd-cli.js, packages/development/lib/trd-cli.js. If missing, print error and HALT.
2. Generate Create normalized executable workstream TRD
- Run: node "$TRD_CLI" create-workstream-trd <TRD_PATHS...> plus --out if provided.
- Parse JSON stdout. If ok is false, process exits non-zero, or JSON malformed: print every error and HALT.
- The generated file MUST contain a Source TRD Manifest, normalized Master Task List, source provenance, verbatim source task markdown payloads, AC-level implementation tasks, AC-level executable test tasks, AC validation tasks, and Definition of Done evidence requirements. Default output path format is docs/TRD/workstreams/TRD-YYYY-<micro_uuid>-workstream-.md.
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.
- 8d ago First seen · 59 lines · 33 tokens per session scan A 7fcef0c595ff
ensemble-create-workstream-trd is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 686 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…
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]".