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-configure-teamgit 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-configure-team)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-configure-team"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-configure-team/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-configure-team"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-configure-team.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.02475 |
| Opus 5 | $0.00016 | $0.01238 |
| Sonnet 5 | $0.00007 | $0.00495 |
| Haiku 4.5 | $0.00003 | $0.00248 |
Grade A, and why
ensemble-configure-team 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:configure-team
This Codex skill mirrors the Ensemble slash command /ensemble:configure-team.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Analyze a Technical Requirements Document (TRD) for complexity and automatically configure team mode. Performs agent and skill discovery, marketplace gap analysis, and injects a
Team Configuration section into the TRD when warranted by project complexity.
Reads the TRD Master Task List to determine team tier (Simple, Medium, Complex) and selects appropriate agents for each detected technical domain.
Workflow
Phase 1: TRD Ingestion
1. Read TRD Document Read and parse the TRD file from the provided path
- Read TRD file from path specified in $ARGUMENTS
- Validate TRD has a Master Task List section
- Validate tasks use TRD-NNN ID format
- Extract document frontmatter (Document ID, PRD reference)
2. Extract Task List Parse the Master Task List into structured task data
- Scan TRD content for entries matching '- [ ] TRD-XXX description (Nh)' pattern
- Extract task ID, description, hour estimate, and annotations from each entry
- Build structured task registry for analysis
- If no tasks found, print error and halt: 'No TRD-NNN tasks found in Master Task List'
Phase 2: Complexity Analysis
1. CLI Flag Parsing Parse $ARGUMENTS for --team and --no-team flags before complexity analysis
- Parse $ARGUMENTS for presence of --team flag; if found set FORCE_TEAM=true
- Parse $ARGUMENTS for presence of --no-team flag; if found set FORCE_NO_TEAM=true
- If both flags present, print ERROR: --team and --no-team are mutually exclusive, and HALT
- Store flag values in FORCE_TEAM and FORCE_NO_TEAM variables for use within this command
2. Task Counter and Hour Estimator Count tasks and total estimated hours from the Master Task List
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 · 207 lines · 33 tokens per session scan A 067c3c0a2850
ensemble-configure-team is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 2,475 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-technical-research
Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".