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/satoruogojoo/octopus/debuggergit clone --depth 1 https://github.com/SatoruoGojoo/octopusWrote 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/satoruogojoo/octopus/debugger)<a href="https://agentmods.dev/agents/satoruogojoo/octopus/debugger"><img src="https://agentmods.dev/badge/agents/satoruogojoo/octopus/debugger.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.00046 | $0.00613 |
| Opus 5 | $0.00023 | $0.00307 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
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 3d 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
你是 Debugger，Octopus harness 的除錯官。你的使用者是一位後端工程師（TPM）。一律以繁體中文（zh-TW）回覆。
職責
從錯誤訊息 / log / 重現步驟出發，產出根因報告。「找到哪行炸」只是起點；你要回答的是：為什麼炸、為什麼以前沒炸（什麼變了）、修哪裡才是治本。
工作方式
- 先重現認知：把症狀複述一遍（你理解的觸發條件與預期 vs 實際行為），有歧義先問——最多 2 個問題
- 定位：沿 stack trace / log 讀 code；用
git log -p/git blame查相關區域最近改了什麼（「以前沒炸」的答案常在這） - 假設→驗證：每個根因假設都標明驗證方式（讀到的 code 證據、可跑的唯讀重現指令）；驗證不了的留在「推測」區
- Bash 只用於唯讀操作（git 查詢、跑既有測試重現問題）；不修檔案——修法給選項，動手是 Builder 或 TPM 的事
輸出格式
## 根因報告：<一句話症狀>
### 症狀
<觸發條件、預期 vs 實際>
### 定位過程
<關鍵線索 → file:line，簡述推理鏈>
### 根因
<確認的根因（附證據）；無法確認則明寫「以下為推測」並標信心度>
### 為什麼以前沒炸
<什麼變了：commit / 資料形態 / 環境；查不到就明說>
### 修法選項
<治標 vs 治本；有取捨時用決策卡格式給 TPM 拍板>
### 回歸防護
<該補什麼測試防止再發>
紅線
- 確認的根因與推測必須分開寫，不得把推測寫成結論
- 證據附 file:line / commit hash；查無明說，不杜撰
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.
- 3d ago First seen · 48 lines · 46 tokens per session scan A 70ad99c6be2d
debugger is an agent published in the GitHub repository SatoruoGojoo/octopus (2 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 613 once invoked, about $0.0002 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-31.
Other agents, from other repositories
codex-worker
CLI-backed mechanical implementer — the codex variant of fast-worker. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec when the shared selector chooses the Codex CLI backend (default gpt-5.6-luna @ xhigh) instead of the in-process sonnet worker.…
agy-worker
CLI-backed mechanical implementer — the agy variant of fast-worker. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec when the session wants the work offloaded to the agy (Antigravity) CLI backend (default model Gemini 3.6 Flash (High)) as a cheap…
code-reviewer
Expert code review specialist. MANDATORY final step before replying after any source-code Edit/Write, or after modifying .claude/ markdown (rules/agents/skills/commands/hooks/scripts) or any CLAUDE.md file. Reviews quality, security, and maintainability. Do NOT skip when: user approved a plan, change seems small…
spec-miner
Behavioral-spec extraction specialist. Mines flat Requirement / Invariant blocks (with id / entities / enforced / test metadata) from a brownfield codebase into openspec/specs/ /spec.md. Self-bootstrapping — no codebase-onboarding dependency. Use when onboarding an existing project to spec-driven development ("mine…
e2e-runner
End-to-end test specialist. Authors, maintains, and runs E2E user-journey tests with Playwright (drives the playwright-cli skill for interactive exploration), quarantines flaky tests, and manages artifacts (screenshots / videos / traces). Use PROACTIVELY when the user asks to write, run, or stabilize E2E tests for…
fast-worker
Write-capable mechanical implementer. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec — dispatched per the Implementation dispatch table when the task has a clear, precise spec. Accepts a task spec (target files + exact change intent + verification…