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 Mathews-Tom/armory --skill debug-investigatorgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/debug-investigator)<a href="https://agentmods.dev/skills/mathews-tom/armory/debug-investigator"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/debug-investigator/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/mathews-tom/armory/debug-investigator"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/debug-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.04261 |
| Opus 5.5 | $0.00021 | $0.01704 |
| Sonnet 5.5 | $0.00011 | $0.00852 |
| Haiku 4.5 | $0.00005 | $0.00426 |
Grade A, and why
debug-investigator 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Investigator
Structured debugging methodology that replaces ad-hoc exploration with hypothesis-driven investigation. Captures symptoms, builds a deterministic feedback loop, analyzes evidence (stacktraces, logs, state), generates ranked hypotheses, designs bisection strategies, identifies instrumentation points, and produces minimal reproductions — documenting every step so dead ends are never revisited.
When to use this skill vs native debugging: The base model handles straightforward debugging (clear stacktraces, obvious errors) natively. Use this skill for non-obvious bugs requiring systematic investigation: intermittent failures, bugs with no clear stacktrace, performance regressions, or issues requiring git bisection and hypothesis ranking.
Reference Files
| File | Contents | Load When |
|---|---|---|
references/stacktrace-patterns.md |
Exception taxonomy, traceback reading, common Python/JS error signatures | Stacktrace or exception present |
references/hypothesis-templates.md |
Bug category catalog, probability ranking, confirmation/refutation tests | Always |
references/bisection-guide.md |
git bisect workflow, binary search debugging, narrowing techniques | Bug appeared after a change |
references/log-analysis.md |
Log pattern extraction, anomaly detection, timeline correlation | Log output available |
references/instrumentation-points.md |
Strategic logging placement, breakpoint strategy, state inspection techniques | Investigation plan needed |
references/upstream/provenance.md |
Source pin, adaptation boundaries, MIT notice and manual resync policy | Attribution/license review or deliberate upstream resync |
What ships with it
9 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.
- 7d ago Changed · +66 lines · -11 tokens per session 9ceebf5218d6
- 1mo ago First seen · 306 lines · 64 tokens per session scan A 85f90b165b84
debug-investigator is a skill published in the GitHub repository Mathews-Tom/armory (337 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 4,261 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
it-ram-doctor
Process tails that hold memory for nothing: finds them and, on the owner's word, kills them. Use on "slow", "swap", "low memory", "kill the tails", "clean up memory", "ram doctor", and after closing heavy apps.
review-with-dora
Use when reviewing agent context (SKILL.md, plugin, rule, AGENTS.md) with dora before reporting done. Also when ask-dora routes a Dora job (review, fix, unused, scan), or the user asks to review, diagnose, or clean up Claude, Cursor, Codex, Copilot, or Grok context.
qa-to-engineering-brief
Converts bug reports, screenshots, user panic, QA notes, and vague complaints into durable engineering briefs. Use when turning observed failures into reproducible issues with severity, expected behaviour, evidence, scope, owner, and acceptance tests.
gke-workload-scaling-troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.