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 agentmods add skills/fortiumpartners/ensemble/ensemble-implement-trdnpx skills add FortiumPartners/ensemble --skill ensemble-implement-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-implement-trd)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-implement-trd"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-implement-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.00036 | $0.01664 |
| Opus 5 | $0.00018 | $0.00832 |
| Sonnet 5 | $0.00007 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00166 |
Grade A, and why
ensemble-implement-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 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:implement-trd
This Codex skill mirrors the Ensemble slash command /ensemble:implement-trd.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
This command implements a complete Technical Requirements Document (TRD) using modern git-town feature branch workflow. It creates a feature branch and delegates to ensemble-orchestrator which routes to tech-lead-orchestrator for structured TDD-based development including planning, implementation, testing, and quality gates.
Workflow
Phase 1: Prerequisites & Feature Branch Setup
1. Git Town Verification Check git-town installation and configuration using validation script
- Execute validation script - bash packages/git/skills/git-town/scripts/validate-git-town.sh
- Handle exit codes - 0 (success), 1 (not installed), 2 (not configured), 3 (version mismatch), 4 (not git repo)
- If validation fails, escalate with specific error message
- Ensure clean working directory (git status)
2. TRD Staleness Gate Check TRD freshness before creating a feature branch. Skip if branch already exists (resume). Algorithm defined in packages/development/skills/staleness-gate/SKILL.md.
- Derive TRD_PATH from $ARGUMENTS (the .md path argument).
- Derive TRD_SLUG from TRD_PATH filename (lowercase, replace non-alphanumeric with hyphens).
- Resume detection: run 'git branch --list feature/<TRD_SLUG>-sprint-1'. If this returns a branch name: IS_RESUME=true. If empty: IS_RESUME=false.
- Execute the TRD Staleness Gate per packages/development/skills/staleness-gate/SKILL.md using TRD_PATH and IS_RESUME.
- On HALT from skill: do not proceed. Implementation stops.
- On RETURN from skill: continue to step 3 (Feature Branch Creation).
3. Feature Branch Creation Create sprint-1 feature branch using git-town skill interview template
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 · 136 lines · 36 tokens per session scan A 49d49e7bef1f
ensemble-implement-trd is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,664 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
pest-testing
Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to…
atdd-team
Use to orchestrate a team-based ATDD workflow — six phases (spec writing, spec review, pipeline generation, implementation, refine, verify & harden) each handled by a fresh agent so no role erodes across a long-running feature. Triggers — "build a feature with a team", "use ATDD with agents", "create an ATDD team"…
atdd
Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The engineer-namespace entry point into the atdd plugin's acceptance workflow. Triggers — "/engineer.atdd", "write the spec", "Checkpoint 3", "formalize the ACs as specs", "generate the test pipeline".
saas-auth
Implement production-ready authentication for SaaS applications including email/password, OAuth social login, session management, and security best practices. This skill covers the complete auth lifecycle from signup through password recovery.
saas-payments
Implement production-ready payment processing with Stripe including one-time payments, recurring subscriptions, customer portal, metered billing, and webhook handling. This skill covers the complete billing lifecycle from checkout through subscription management.
saas-analytics
Implement product analytics for understanding user behavior, tracking key metrics, and making data-driven decisions. Covers event tracking, user identification, cohort analysis, and integration with analytics platforms like PostHog, Mixpanel, or custom solutions.