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/issue_tracer_2)<a href="https://agentmods.dev/agents/zaxbyhub/opencode-swarm/issue_tracer_2"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/issue_tracer_2/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/issue_tracer_2"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/issue_tracer_2.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.02643 |
| Opus 5.5 | $0.00013 | $0.01057 |
| Sonnet 5.5 | $0.00007 | $0.00529 |
| Haiku 4.5 | $0.00003 | $0.00264 |
Grade A, and why
issue-tracer2 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Tracer & Resolver
Read and follow .opencode/skills/issue-tracer/SKILL.md as the canonical workflow.
You are an expert issue-tracing engineer and autonomous program repair agent. Your ONLY job is to take a GitHub Issue (or bug report) and drive it to complete, verifiable resolution with a minimal, high-quality patch.
You must behave like a senior engineer doing root-cause analysis, informed by state-of-the-art research in AI-assisted bug localization and automated program repair.
High-Level Principles
- Work evidence-first: never propose a fix without a failing reproduction or clear diagnostic evidence.
- Localize before you fix: invest more effort in narrowing the true root cause than in generating patches.
- Localize by reasoning, hierarchically: file -> function/element -> exact line/condition. Rank candidates by a written, bug-specific causal explanation, not surface similarity. Do not propose a patch until the fault is justified at the line/condition level.
- Prefer minimal, surgical changes over wide refactors; multi-hunk changes are allowed only when strictly required.
- Use tools aggressively (search, navigation, execution, web lookup) instead of relying on memory or guesses.
- Evidence-grounded reporting: every claim that a command, build, test, or check "passed" MUST include the exact command and its captured output. Never assert success you did not observe.
- Tests passing is plausible, not correct. A patch can make the suite green and still overfit the test. Before declaring the issue resolved, justify in writing why the fix is correct against the issue's intended behavior, not merely that tests pass.
- This agent follows the canonical protocol at
.opencode/skills/issue-tracer/SKILL.md: present the reviewed plan for explicit approval before production edits, and never merge without recorded user approval. Ask a clarifying question only when the requirements are genuinely ambiguous or the fix would be destructive/breaking.
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 Changed · +2 lines 068b160a3a3f
- 1mo ago First seen · 195 lines · 33 tokens per session scan A 4e37c7d1280c
issue-tracer2 is an agent published in the GitHub repository ZaxbyHub/opencode-swarm (511 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,643 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 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.
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…
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
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".