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 bromso/metapowers --skill debuggit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/debug)<a href="https://agentmods.dev/skills/bromso/metapowers/debug"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/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/bromso/metapowers/debug"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/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.00052 | $0.00540 |
| Opus 5.5 | $0.00021 | $0.00216 |
| Sonnet 5.5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
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 2d 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
Investigate and fix the issue described in "$ARGUMENTS" using systematic root cause analysis. No guessing — find the cause before attempting fixes.
Prerequisites
None — this is a utility skill that can run anytime a bug is encountered.
Process
Phase 1: Investigation
-
Read error messages carefully:
- Read the full error output, stack trace, and any warnings
- Note file paths, line numbers, and error codes
- Don't skip past errors — they often contain the solution
-
Reproduce the issue:
- Identify the exact steps to trigger the bug
- Can it be triggered reliably?
- If not reproducible, gather more data before proceeding
-
Check recent changes:
- What changed recently that could cause this? (git log, git diff)
- New dependencies, config changes, environment differences?
Phase 2: Analysis
-
Trace the data flow:
- Where does the bad value originate?
- Trace backward through the call stack to the source
- Fix at the source, not at the symptom
-
Find working examples:
- Is there similar code that works correctly?
- What's different between working and broken?
Phase 3: Hypothesis
-
Form a single hypothesis:
- State clearly: "I think X is the root cause because Y"
- Be specific, not vague
-
Test minimally:
- Make the smallest possible change to test the hypothesis
- One variable at a time
- If it doesn't work, form a NEW hypothesis — don't pile fixes
Phase 4: Fix
-
Write a failing test that reproduces the bug
-
Implement the fix — address the root cause, not the symptom
-
Verify:
- The failing test now passes
- No other tests broke
- The original issue is resolved
-
Commit the fix with a clear message explaining what was wrong and why
Output
Present findings to the user:
- What the root cause was
- What was changed to fix it
- The commit hash
- Any related issues discovered during investigation
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.
- 2d ago First seen · 75 lines · 52 tokens per session scan A 0a26e6dc4d47
debug is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 540 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-10-21.
Other skills, from other repositories
laravel-testing
Use when testing controllers, services, or models, or implementing TDD on Laravel 13 with Pest 5 / PHPUnit 13 (or Pest 4 / PHPUnit 12 on PHP 8.3).
php-testing
Use when writing/configuring tests on a non-Laravel PHP project — PHPUnit vs Pest. Do NOT use for Laravel test helpers or quality tooling (php-quality-tooling).
react-testing
Testing Library for React 19 - render, screen, userEvent, waitFor, Suspense. Use when writing tests for React components with Vitest.
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).
go-testing-quality
Use when writing or reviewing Go tests, adding coverage, benchmarking, or profiling a Go program. Not for CI/lint wiring (go-tooling-security) or non-Go tests.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.