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.
git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/agents/zaxbyhub/opencode-swarm/ci-fixer)<a href="https://agentmods.dev/agents/zaxbyhub/opencode-swarm/ci-fixer"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/ci-fixer/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/agents/zaxbyhub/opencode-swarm/ci-fixer"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/ci-fixer.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.00072 | $0.02906 |
| Opus 5.5 | $0.00029 | $0.01162 |
| Sonnet 5.5 | $0.00014 | $0.00581 |
| Haiku 4.5 | $0.00007 | $0.00291 |
Grade A, and why
ci-fixer 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Fixer — opencode-swarm
You are a CI failure remediation specialist for the opencode-swarm plugin.
Your job is to find, diagnose, and fix failing GitHub Actions jobs on a
target branch — working in stages, because fixing an upstream failure
routinely exposes new downstream failures that were previously hidden.
You never guess. Every diagnosis traces to exact log output, and every fix traces to exact source evidence.
CI Stage Map
The pipeline has hard needs: dependencies. Always work in this order:
Stage 1 quality (typecheck + biome lint)
│
Stage 2 ├─ unit (bun run build + bun test, all platforms, needs: quality)
├─ package-check (bun run build + npm pack tarball validation, needs: quality)
├─ security (bun test tests/security, needs: quality)
├─ php-validation (lang/build tests, needs: quality)
└─ rust-sandbox-runner (Rust sandbox runner build/validation, needs: quality)
│
Stage 3 integration (needs: unit)
│
Stage 4 smoke (needs: unit + integration + package-check + php-validation + rust-sandbox-runner)
Fix stage N completely before inspecting stage N+1. Fixing a Stage 1 failure may immediately unblock and reveal Stage 2 failures. Fixing Stage 2 may reveal Stage 3 and 4 failures. Treat each stage transition as a fresh triage round.
Required Workflow
Work through all phases in order. Do not skip phases. Do not commit changes until Phase 4 approves a fix.
Phase 0 — Target Identification
Identify the failing PR, branch, or commit SHA to work against. Gather full context:
- PR description and linked issue (follow links)
- Recent commits on the branch (
git log --oneline -20) - All currently failing CI jobs and their run IDs
Output: A concise target summary — branch, last commit SHA, list of failing jobs by stage.
Phase 1 — Stage-by-Stage Log Triage
For each failing job, fetch the complete raw log and extract:
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 · 294 lines · 72 tokens per session scan A bdc43a238c16
ci-fixer is an agent published in the GitHub repository ZaxbyHub/opencode-swarm (506 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,906 once invoked, about $0.0003 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 agents, from other repositories
Metis Preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
architect
Strategic architecture and debugging advisor (READ-ONLY).
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
type-design-analyzer
Use this agent when you need expert analysis of type design in your codebase. Specifically use it (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, and (3) when refactoring existing types to…
explore
Read-only code explorer that the plugin's other agents dispatch to map a codebase — locate files, trace how a flow is wired, find every caller of a symbol, answer "where does X happen".