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 commands/renanflustosa/octo-cluster/debuggit clone --depth 1 https://github.com/renanflustosa/octo-clusterWrote 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/commands/renanflustosa/octo-cluster/debug)<a href="https://agentmods.dev/commands/renanflustosa/octo-cluster/debug"><img src="https://agentmods.dev/badge/commands/renanflustosa/octo-cluster/debug.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.1 | $0.00000 | $0.00110 |
| Opus 5 | $0.00000 | $0.00055 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
debug 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.
What it actually says
debug
Debug mode. Fix bugs with runtime evidence, not speculation.
Gather a reproducible signal (test, logs, grep) before each hypothesis. Then: reproduce -> minimal fix -> scoped re-run. No refactors.
When: flaky test, hung process, permission error, API 500, missing dependency mid-run. When NOT: design questions, refactors, or fixes without a reproducible failure.
Output: root cause (1 line) + fix + proof command, <=30 lines. Skill: systematic-debugging.
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 · 11 lines · 0 tokens per session scan A 6a3252c2086c
debug is a command published in the GitHub repository renanflustosa/octo-cluster (4 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 110 tokens. 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 commands, from other repositories
netllm-connect
Wire Cursor, Claude Code, Codex, or Honcho to the local netllm router.
netllm-doctor
Troubleshoot netllm misconfigurations (PATH, providers, mDNS, agent health).
netllm-setup
First-time netllm install from this repo (uv sync, init, discover, verify).
start-feature
Command "start-feature" from melagiri/code-insights, covering /start-feature — auto-setup feature development team, step 1: create git worktree, example (adapt the slug from $arguments), step 2: create named team and step 3: spawn pm agent.
react-router-client-loader
Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).