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-implement-beadgit 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-bead)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-implement-bead"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-implement-bead/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-implement-bead"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-implement-bead.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.00033 | $0.01930 |
| Opus 5.5 | $0.00013 | $0.00772 |
| Sonnet 5.5 | $0.00007 | $0.00386 |
| Haiku 4.5 | $0.00003 | $0.00193 |
Grade A, and why
ensemble-implement-bead 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:implement-bead
This Codex skill mirrors the Ensemble slash command /ensemble:implement-bead.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Implement a single beads task identified by its bead ID. Fetches bead details, creates a feature branch, analyses the codebase, implements the required changes, runs tests, then closes the bead and creates a pull request.
Designed for focused single-task execution — use /ensemble:beads-build for multi-task epic-level orchestration. Records all state transitions in beads for cross-session visibility.
Key behaviors:
- Validates bead exists and is not already closed before starting
- Warns (does not halt) on dirty working directory
- Derives branch name from bead title with bead/- prefix
- Marks bead in_progress before implementing; closed on success
- Records br comments at each state transition
- Creates PR via gh pr create on completion
Workflow
Phase 1: Preflight
1. Argument Parsing Extract bead ID from arguments or prompt user if missing
- Parse $ARGUMENTS: extract first token as BEAD_ID (e.g., "beads-042" or "42"); if $ARGUMENTS is empty, prompt user: "Please provide a bead ID (e.g., beads-042):" and store response as BEAD_ID
- Normalise BEAD_ID: if numeric only (e.g., "42"), leave as-is — br accepts bare integers; store original input as BEAD_ID_RAW
2. Tool Availability Check Verify br is installed and functional
- "which br || { echo 'ERROR: br (beads_rust) not installed. Install from https://github.com/Dicklesworthstone/beads_rust'; exit 1; }"
- "br list --status=open > /dev/null 2>&1 || { echo 'ERROR: br not functional — check beads store'; exit 1; }"
3. Bead Validation Fetch bead details and verify it is actionable
- Run: br show <BEAD_ID> — if exit code != 0 print "ERROR: Bead <BEAD_ID> not found." and EXIT
- Parse bead fields from output: store BEAD_TITLE, BEAD_STATUS, BEAD_TYPE, BEAD_DESCRIPTION
- If BEAD_STATUS == "closed": print "Bead <BEAD_ID> is already closed." and EXIT
- Print bead summary: "Bead: <BEAD_ID> | Status: <BEAD_STATUS> | Type: <BEAD_TYPE> | Title: <BEAD_TITLE>"
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 · 155 lines · 33 tokens per session scan A 315f194c73b4
ensemble-implement-bead is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 1,930 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
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
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-create-epics-and-stories
Break requirements into epics and user stories. Use when the user says "create the epics and stories list".
bmad-correct-course
Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change".
bmad-retrospective
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]".
bmad-sprint-planning
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan".