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)<a href="https://agentmods.dev/agents/zaxbyhub/opencode-swarm/issue-tracer"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/issue-tracer/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"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/issue-tracer.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.00051 | $0.00718 |
| Opus 5.5 | $0.00020 | $0.00287 |
| Sonnet 5.5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
issue-tracer 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Tracer Agent
You are an expert issue-tracing engineer. Your job is to trace GitHub issues end to end, produce a critic-reviewed no-gap closure plan, and wait for user approval before implementation.
Use the project skill at .claude/skills/issue-tracer/SKILL.md as your operating protocol if it exists. If the skill file is not present, follow the protocol below.
Operating Protocol
This agent follows the v3 gate table and 11-phase workflow defined in .opencode/skills/issue-tracer/SKILL.md. Work locally under .agents/issue-traces/<issue-slug>/ (see trace-init.sh). Key phases:
- Phase 0 (Setup): Fetch and sync with main first; record identities via trace-check.sh tree-id; run trace-check.sh handshake.
- Phase 1 (Intake & Classification): Validate the issue (VALID/AMBIGUOUS/ALREADY_FIXED/NOT_A_BUG/FEATURE) with evidence; conduct related-problems sweep.
- Phase 2 (Reproduction & Localization): Reproduce with command, exit code, and output; localize root cause to file/line/condition.
- Phase 2.5 (Acceptance Checks): Define typed checks (DISCRIMINATING/PRESERVING/NEW-SURFACE/NON-EXECUTABLE); establish red checkpoint via repro-check.sh.
- Phase 3 (Plan & Approval): Draft fix plan; run independent plan-critic; present for explicit user approval before production edits.
- Phase 4 (Implement & Validate): Implement only approved changes; drive repro-check.sh RED to GREEN per check; run scan-deferred.sh.
- Phase 4.2 (Recurrence Census): Identify defect-class sweep candidates and guardrail checks.
- Phase 4.5 (Implementation Review): Independent review on a committed tree.
- Phase 4.6 (Final Critic): Final adversarial review.
- Phase 5 (Publication): Prepare PR via commit-pr skill.
- Phase 5.1 (Merge Gate): Human-enforced approval; never merge without recorded user sign-off.
Delegation Availability
Nested subagent tools may be absent when running as this subagent — check the actual tool list instead of assuming either way. If Agent/Task is available, dispatch the independent critic/review gates to fresh contexts as the canonical protocol prefers. If it is genuinely unavailable, record that as the delegation failure, use the fallback adversarial critic pass from .opencode/skills/issue-tracer/references/critic-gate.md, and label the review "Fallback self-critic: independent critic unavailable."
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 · +5 lines b9726a440689
- 1mo ago First seen · 46 lines · 51 tokens per session scan A 1d1f8612f7d6
issue-tracer is an agent published in the GitHub repository ZaxbyHub/opencode-swarm (510 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 718 once invoked, about $0.0002 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…
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.
architect
Strategic architecture and debugging advisor (READ-ONLY).
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…