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-beads-buildgit 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-beads-build)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-beads-build"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-beads-build/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-beads-build"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-beads-build.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.00035 | $0.09425 |
| Opus 5.5 | $0.00014 | $0.03770 |
| Sonnet 5.5 | $0.00007 | $0.01885 |
| Haiku 4.5 | $0.00003 | $0.00942 |
Grade A, and why
ensemble-beads-build 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 1mo 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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:beads-build
This Codex skill mirrors the Ensemble slash command /ensemble:beads-build.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Drive an existing bead hierarchy (epic -> stories -> tasks) to completion through the full builder -> code-review -> close pipeline. This is the canonical build engine — works for raw beads with no TRD required. implement-trd-beads --execute is effectively a TRD-augmented version of this command.
Uses bv --robot-next for graph-aware task selection (required) or br ready as fallback. Records all state transitions in beads for cross-session resumability. When --trd is provided, enables TRD augmentations: traceability tokens, TRD checkbox sync, and requirement satisfaction report.
Key behaviors:
- bv --robot-next determines what to run next (fallback: br ready)
- Quality gates: phase completion triggers test delegation; results recorded as br comments
- Sync: br sync --flush-only before every bv call
- Wheel instructions: printed every run with NTM spawn commands for multi-agent flywheel
- Graceful degradation: bv features skipped if bv unavailable; br required
- TRD mode: optional --trd flag enables traceability tokens, checkbox sync, requirement report
Workflow
Phase 1: Preflight
1. Argument Parsing Parse epic-id or slug pattern, --trd path, --strategy, and max parallel N
- Parse $ARGUMENTS: if first token matches pattern beads-NNN or a numeric ID, treat as direct epic bead ID (EPIC_ID_MODE=true); otherwise treat as slug pattern (EPIC_ID_MODE=false)
- Parse --trd from $ARGUMENTS (optional); if present set TRD_MODE=true and TRD_PATH=; if absent set TRD_MODE=false
- Parse --strategy from $ARGUMENTS (optional); valid values: tdd, characterization, bug-fix, refactor, test-after, flexible
- Parse "max parallel N" from $ARGUMENTS (e.g., "max parallel 3") — default MAX_PARALLEL=1 if not present
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.
- 1mo ago First seen · 468 lines · 35 tokens per session scan A 42856f8ac5d3
ensemble-beads-build is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 9,425 once invoked, about $0.0001 per session on Opus 5.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
product-direction
Judges feature requests, feature pull requests and your own proposals against a repository's written product direction, gives a cited verdict, and records each new no. Use when triaging, labelling or replying to a feature request or a feature pull request, including as an autonomous triage agent; when asked whether a…
bmad-review-edge-case-hunter
Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
bmad-code-review
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code".
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-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
bmad-create-epics-and-stories
Break requirements into epics and user stories. Use when the user says "create the epics and stories list".