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 agentmods add agents/zaxbyhub/opencode-swarm/issue-tracergit 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.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.00558 |
| Opus 5 | $0.00026 | $0.00279 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
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 5d 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 — 46 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
- Read the issue and repository evidence before making claims.
- Reproduce the issue or document why it cannot be reproduced.
- Localize the root cause to file, symbol, line range, broken contract, and triggering condition.
- Write artifacts under
.agents/issue-traces/<issue-slug>/(create the directory and its.git/info/excludeentry with the skill's.opencode/skills/issue-tracer/scripts/trace-init.sh <issue-slug>, run from the repo root). Derive<issue-slug>as lowercase kebab-case,[a-z0-9-]only — the script rejects anything else. - Produce 3-5 fix candidates when realistic and rank them.
- Run a critic pass before presenting a plan.
- Present the reviewed plan and wait for explicit user approval before editing production code.
- After approval, implement only the approved minimal fix, add regression protection, run impacted checks, and prepare PR-ready output.
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."
Final Output Before Approval
Return:
- issue summary
- reproduction evidence
- root cause with exact file/symbol/line references
- fix candidates and selected plan
- impact analysis
- test plan
- critic verdict and revisions
- explicit approval request
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.
- 5d 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 (462 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 558 once invoked, about $0.0003 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 agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase. This is a single-context repo.
issue-tracker
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
triage-labels
The skills speak in terms of five canonical triage roles. On this repo the tracker is the dev-3.0 Kanban board (see docs/agents/issue-tracker.md), so each role is a dev3 label applied to the task. dev3 statuses/columns (todo, in-progress, user-questions, review-by-ai, review-by-user) are managed by hooks and are NOT…
Claude Code Engineer
Use when: developing, debugging, refactoring, reviewing, exploring, or explaining code in the Claude Code CLI codebase. Covers all engineering tasks including feature implementation, bug fixes, code review, architecture analysis, and codebase navigation.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
ap-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.