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-fix-issuegit 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-fix-issue)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-fix-issue"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-fix-issue/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-fix-issue"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-fix-issue.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.00027 | $0.00480 |
| Opus 5.5 | $0.00011 | $0.00192 |
| Sonnet 5.5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
ensemble-fix-issue 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.
What it actually says
Ensemble Command: /ensemble:fix-issue
This Codex skill mirrors the Ensemble slash command /ensemble:fix-issue.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
Orchestrate a complete bug fix workflow from analysis to PR creation, assembling a virtual team of specialized agents (Product Manager, Tech Lead, Architect, QA Lead) to ensure high-quality fixes with minimal user intervention.
Workflow
Phase 1: Analysis & Planning
1. Codebase Analysis Explore codebase to identify affected files, patterns, and scope. Use Grep, Glob, and Read tools to understand context.
2. Collaborative Planning Assemble virtual team of 4 specialized agents to create comprehensive fix plan with multiple perspectives.
3. User Interview (Conditional) If issue description is ambiguous or --interactive flag is set, ask clarifying questions ONE AT A TIME (max 5) -- never batch questions. Use AskUserQuestion for each. Wait for each answer before asking the next.
Phase 2: Execution
1. Branch Creation Create git branch with conventional naming
2. Task List Generation Break down plan into actionable tasks
3. Task Execution Execute all tasks with appropriate agent delegation and real-time progress tracking.
Phase 3: Validation & Delivery
1. Test Validation Run test suite with auto-fix retry logic. Ensure all tests pass before creating PR.
2. PR Creation Create comprehensive pull request with GitHub CLI
Expected Output
Format: Pull Request
Structure:
- Git Branch: Feature branch following fix/issue-{num}-{slug} convention
- Code Changes: Implementation fixes with test coverage
- Pull Request: Comprehensive PR with problem, solution, changes, and test plan
Usage
/ensemble:fix-issue
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 · 78 lines · 27 tokens per session scan A c5b6e0bee96b
ensemble-fix-issue is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 6d ago), licensed MIT. It adds 27 tokens to every session and 480 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
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
issue-assessment
Use when triaging a GitHub issue for gflow-cli — a reporter's bug claim, a freshly-filed issue, or deciding whether and how to act on one. Also use when an autonomous agent (hermes-ops) picks up a labelled issue. Read-only: produces a verdict, an end-to-end-verifiability judgment, and a reporter-facing reply. Does not…
merge
Resolve an in-progress merge or rebase by the intent of both sides, re-run the full gate on the merged tree, and finish the operation.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
pixiv-cli-ci
Diagnose pixiv-cli GitHub Actions failures and verify current-head quality, platform, PR-verification, native/browser, and release evidence. Use for CI readiness, failed or stalled runs, or an explicitly authorized rerun/cancel/dispatch; default to read-only evidence gathering.