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-refine-trdgit 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-refine-trd)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-full-refine-trd"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-full-refine-trd/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-full-refine-trd"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-full-refine-trd.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.03097 |
| Opus 5 | $0.00023 | $0.01548 |
| Sonnet 5 | $0.00009 | $0.00619 |
| Haiku 4.5 | $0.00005 | $0.00310 |
Grade A, and why
ensemble-full-refine-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 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.
This is a copy
91% identical to ensemble-refine-trd — 184 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ensemble:refine-trd
Mission: Refine and enhance an existing Technical Requirements Document based on stakeholder feedback, additional research, or identified gaps. Updates TRD while maintaining version history, traceability, and Design Readiness scoring.
Constraints:
- DO NOT implement, build, or execute any technical work described in the TRD
- This command ONLY refines the TRD document itself
- The arguments describe what should be improved in the document, not what should be built
- After refining the TRD, stop and wait for user approval before any implementation
- DO NOT make any edits during Synthesis -- findings are presented first, edits happen only after user selects items
Phase 1: TRD Review
Step 1: Current TRD Analysis
Review existing TRD content and extract structural metadata
Actions:
- Read the TRD file from the path provided in $ARGUMENTS
- Parse frontmatter for Document ID (TRD-YYYY-NNN), Version, PRD reference, Design Readiness Score
- Count total tasks (TRD-NNN pattern), total test tasks (TRD-NNN-TEST), total hours estimated
- Build dependency graph from [depends: TRD-NNN] annotations
- Check if Acceptance Criteria Traceability matrix exists
- Note current version number for bumping later
- PR format detection: scan TRD for '### PR ' followed by a digit within the '## Master Task List' section (from '## Master Task List' heading to the next '##' heading or EOF). If found: set PR_FORMAT=true and log 'TRD format: PR-stack'. Else: set PR_FORMAT=false and log 'TRD format: legacy phase/sprint'.
- If PR_FORMAT=true: count PR boundary sections; for each ### PR N: heading check whether a Shippable State: line immediately follows it; record MISSING_SHIPPABLE[N] for any that don't; record INFRA_ONLY_SHIPPABLE[N] for any whose Shippable State text contains only infrastructure language (e.g., 'scaffolding', 'setup done', 'infrastructure complete') with no user-observable capability.
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 · 214 lines · 45 tokens per session scan A 67459442bd7f
ensemble-full-refine-trd is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 3,097 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to ensemble-refine-trd, differing in 184 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…
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-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]".
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".