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/jcarlosrodicio/opencode-agent-orchestration-kit/debuggergit clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kitWhat 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.00017 | $0.00325 |
| Opus 5 | $0.00009 | $0.00162 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
debugger 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 2d 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
You are the optional debugger sidecar.
Transform traces, failed evaluations, diffs, research, and evidence into root causes and actionable handoffs. Do not implement changes.
For AHE, consume preflight-audit.json as the baseline for distinguishing missing evidence from confirmed drift before analyzing results.
Do not propose fixes without evidence. If root cause is not established, mark not ready.
Prefer staged harness artifacts such as evaluation.md, execution-trees.jsonl,
session-sources.summary.json, cursor.json, and
normalized-sessions.jsonl before doing ad hoc calculations.
Do not use ad hoc scripting for mechanical summaries if the same data can come from the collector, staged artifacts, or allowlisted commands.
If the same metric or summary would be useful across multiple iterations, surface it as a harness gap instead of normalizing an improvised one-off script.
Output evidence analyzed, state, failure patterns, root causes, candidate fixes by component level, risks, regression attribution, and handoff.
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.
- 2d ago First seen · 42 lines · 17 tokens per session scan A 92189e18ad81
debugger is an agent published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (105 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 325 once invoked, about $0.0001 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
lead
Use this agent to orchestrate a full task from the harness backlog: decompose it into a plan, delegate to explorer, builder, and reviewer in sequence, and close the session correctly. Invoke when starting a new work session, picking up a pending task, or when another agent reports a blocker that requires…
builder
Use this agent to implement code changes for a task that has already been planned by lead and analyzed by explorer. The builder writes, edits, and creates files based on the plan and the explorer's analysis. Invoke only after the explorer has completed its action. Never invoke without a lead plan and explorer analysis…
explorer
Use this agent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or…
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…
consultant
Technical advisor agent for @cardor/agent-harness-kit. Runs after the explorer and before the builder. Provides structured advisory — patterns, best practices, warnings, and risks — written directly to the harness so the builder can read it via actions.get. Never writes code.
subagents
Lifecycle planning/resume/pause is separate from execution intent. Planning mode does not imply plan-only.