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-requirement-statusgit 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-requirement-status)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-requirement-status"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-requirement-status/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-requirement-status"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-requirement-status.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.00032 | $0.01643 |
| Opus 5 | $0.00016 | $0.00822 |
| Sonnet 5 | $0.00006 | $0.00329 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
ensemble-requirement-status 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 10d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:requirement-status
This Codex skill mirrors the Ensemble slash command /ensemble:requirement-status.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Scan the root epic bead and all child task beads for req-verified: tokens written by implement-trd-beads when test tasks close. Cross-reference against the PRD REQ-NNN list to produce a requirement satisfaction table showing which requirements are verified, which are in-progress, and which are not yet started.
Workflow
Phase 1: Context Resolution
1. TRD Slug Resolution Resolve the TRD slug from $ARGUMENTS. If $ARGUMENTS is a file path: derive TRD_SLUG from filename (lowercase, replace non-alphanumeric with hyphens). If $ARGUMENTS is a slug string: use directly as TRD_SLUG. If $ARGUMENTS empty: list recent TRD-prefixed epics via br list --status=open --json and prompt user. If br list returns no TRD-prefixed epics: print 'No TRD implementations found in beads storage. Run /ensemble:implement-trd-beads first.' and EXIT.
2. Root Epic Location Find the root epic bead for this TRD. Run: br list --status=open --json Verify the output is valid JSON (starts with '['). If not: print 'ERROR: br command failed or returned non-JSON output. Is br installed and configured? Output: <first 200 chars>' and EXIT. Also run: br list --status=closed --json Verify the output is valid JSON (starts with '['). If not: print 'ERROR: br command failed or returned non-JSON output. Is br installed and configured? Output: <first 200 chars>' and EXIT. Parse combined JSON output, search for entry where title matches [trd:<TRD_SLUG>] with type epic. If found: ROOT_EPIC_ID = bead .id If not found: print 'ERROR: No root epic found for TRD slug <TRD_SLUG>. Run implement-trd-beads first.' and EXIT.
3. PRD Requirement Loading Load PRD REQ-NNN list for cross-reference. Search TRD document for PRD reference link or 'Based on PRD:' annotation. If TRD has a PRD reference line AND the file exists at that path: parse PRD for REQ-NNN IDs -> build PRD_REQUIREMENTS map. If TRD has a PRD reference line BUT the file does not exist at that path: print 'WARNING: PRD file referenced in TRD not found at . Cross-reference reporting will be incomplete. Fix the PRD path in the TRD.' Set PRD_REQUIREMENTS = null. If TRD has no PRD reference line at all: print 'NOTE: No PRD reference in TRD — cross-reference not available.' Set PRD_REQUIREMENTS = null.
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.
- 10d ago First seen · 131 lines · 32 tokens per session scan A 1f8eab1b3a13
ensemble-requirement-status is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 1,643 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-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".