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-featurenpx skills add FortiumPartners/ensemble --skill ensemble-featuregit 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-feature)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-feature"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-feature.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.00046 | $0.01669 |
| Opus 5 | $0.00023 | $0.00834 |
| Sonnet 5 | $0.00009 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
ensemble-feature 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:feature
This Codex skill mirrors the Ensemble slash command /ensemble:feature.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Orchestrate the complete idea-to-plan pipeline as a single command. Runs five commands in strict sequence: (1) create-prd, (2) refine-prd, (3) create-trd, (4) refine-trd, (5) implement-trd-beads --plan. Each step completes before the next begins. Refinement steps (2 and 4) pause for user input via AskUserQuestion. The --skip-refine flag bypasses both refinement steps for an uninterrupted run. Planning only -- no code is executed. Terminates with a handoff message showing how to start implementation.
Workflow
Phase 1: Argument Parsing
1. Parse Arguments and Set Variables Parse $ARGUMENTS and initialize pipeline variables.
-
If $ARGUMENTS is empty or blank, print the following and exit without running any pipeline step: Usage: /ensemble:feature [--skip-refine]
-
Scan $ARGUMENTS for the --skip-refine token. If found, set SKIP_REFINE=true and remove the token from the remaining text. If not found, set SKIP_REFINE=false.
-
Scan the remaining text for any other tokens that begin with --. If any unknown flag is found, print the following and exit without running any pipeline step: Error: Unknown flag ''. Only --skip-refine is supported. Usage: /ensemble:feature [--skip-refine]
-
Set FEATURE_DESCRIPTION to the remaining argument text after removing --skip-refine if it was present. Preserve the description verbatim -- no transformation, truncation, or summarization.
Phase 2: Pipeline Execution
1. Step 1 - create-prd Print: [Step 1/5] create-prd...
Invoke /ensemble:create-prd with FEATURE_DESCRIPTION as the argument. Pass the description verbatim with no modification.
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 · 167 lines · 46 tokens per session scan A 6c063b6b1fe2
ensemble-feature is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,669 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…
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.
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.
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-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-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]".