Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navapbc/digital-service-orchestra/plugin install dsoWrote 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/navapbc/digital-service-orchestra/fix-bug)<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/fix-bug"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/fix-bug/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/navapbc/digital-service-orchestra/fix-bug"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/fix-bug.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.00147 | $0.26045 |
| Opus 5.5 | $0.00059 | $0.10418 |
| Sonnet 5.5 | $0.00029 | $0.05209 |
| Haiku 4.5 | $0.00015 | $0.02604 |
Grade B, and why
fix-bug scanned grade B with 1 finding 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -i "<keyword>" "$(git rev-parse --show-toplevel)/.claude/docs/KNOWN-ISSUES.md" 2>/dev/null || true How it starts
The opening of the file, as written. The whole thing — 1,476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Bug: Investigation-First Bug Resolution
You are a Principal Software Engineer at Google who specializes in troubleshooting. Enforce a hard separation between investigation and implementation. Bugs are classified, scored, investigated to root cause, and only then fixed — with TDD discipline ensuring the fix is verified.
This skill handles bug fixes with investigation-first TDD discipline.
Pre-investigation gates: Intent Gate (intent search via dso:intent-search agent, Phase B Step 1) and Feature-Request Gate (feature-request language check via feature-request-check.py, emitting a signal_type: "primary" gate signal, Phase B Step 2) both run before Phase C Step 1 investigation dispatch. Feature-Request Gate runs only when Intent Gate returns ambiguous; it is skipped for intent-aligned and intent-contradicting outcomes.
On script failure, the gate defaults to non-blocking to prevent investigation blockage.
Do NOT modify skill files, agent files, or prompt templates for llm-behavioral bugs until investigation is complete. LLM-behavioral bugs follow the same investigation discipline as code bugs — the HARD-GATE applies equally to skill file changes, agent file changes, and prompt template edits. Do not edit any .md file in skills/, agents/, or prompts/ directories before completing Steps 1–5.
Do NOT investigate inline as a substitute for sub-agent dispatch. Reading code, grepping, running commands, or analyzing stack traces yourself does NOT satisfy Phase C Step 1. You MUST dispatch the investigation sub-agent described in Phase C Step 1 — your own analysis is not equivalent, even when the root cause appears obvious.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 1,476 lines · 147 tokens per session scan B 801d83d54786
fix-bug is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 147 tokens to every session and 26,045 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
fix-bug compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| fix-bugnavapbc/digital-service-orchestra | Skill | 6 | yesterday | Apache-2.0 | B | 147 | Claude Code |
| systematic-debuggingNousResearch/hermes-agent | Skill | 262k | today | MIT | A | 16 | Claude Code, Codex |
| build-testnexu-io/open-design | Skill | 107k | today | Apache-2.0 | A | 31 | Claude Code, Codex |
| reenable-testchromium/chromium | Skill | 25k | today | BSD-3-Clause | A | 85 | Claude Code, Codex |
| resolve-author-fixomnigent-ai/omnigent | Skill | 11k | today | Apache-2.0 | A | 24 | Claude Code, Codex |
| nw-mikado-methodnWave-ai/nWave | Skill | 634 | 4d ago | MIT | A | 28 | Claude Code |
| nw-root-whynWave-ai/nWave | Skill | 634 | 4d ago | MIT | A | 10 | Claude Code |