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 skills add arbiterForge/codeArbiter --skill debuggit clone --depth 1 https://github.com/arbiterForge/codeArbiterWrote 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/skills/arbiterforge/codearbiter/debug)<a href="https://agentmods.dev/skills/arbiterforge/codearbiter/debug"><img src="https://agentmods.dev/badge/skills/arbiterforge/codearbiter/debug/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/skills/arbiterforge/codearbiter/debug"><img src="https://agentmods.dev/badge/skills/arbiterforge/codearbiter/debug.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.00068 | $0.02197 |
| Opus 5 | $0.00034 | $0.01099 |
| Sonnet 5 | $0.00014 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00220 |
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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 100 lines · 68 tokens per session scan A 3968709d6421
debug is a skill published in the GitHub repository arbiterForge/codeArbiter (142 stars, last pushed today), licensed AGPL-3.0. It adds 68 tokens to every session and 2,197 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-09-03.
Other skills, from other repositories
patch-or-fix
Evidence-gated post-fix review that classifies whether a bug change removes the root cause or only masks the symptom. Any invocation, including a one-sentence prompt, requires the full canonical workflow and Required Output sections: Evidence Ledger, Assumption Ledger, Boundary Ledger, Specialist Reviews, Causal…
enterprise-forge
Use when reviewed enterprise work still needs adversarial probing, mechanical checks, and recycle-loop bug closure before final verification.
prove-it
Post-fix runtime proof gate. Use after Codex implements or reviews a bug fix, feature fix, PR, workflow change, or claimed repair; before saying fixed/done, committing, opening a PR, merging, or shipping. Requires mandatory blast-radius, review-feedback trap replay, actual runtime evidence at the boundary where the…
run-verification
Run the full verification pipeline (lint, unit tests, E2E if UI changed) — invoke after code changes.
agent-debug-fixer
A Chinese-language debugging and repair workflow for software problems. It investigates errors, failed tests, broken pages, or behavior that does not match expectations, then makes a minimal fix.
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.