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 trinhhaox/ag-kit --skill systematic-debugginggit clone --depth 1 https://github.com/trinhhaox/ag-kitWrote 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/trinhhaox/ag-kit/systematic-debugging)<a href="https://agentmods.dev/skills/trinhhaox/ag-kit/systematic-debugging"><img src="https://agentmods.dev/badge/skills/trinhhaox/ag-kit/systematic-debugging/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/trinhhaox/ag-kit/systematic-debugging"><img src="https://agentmods.dev/badge/skills/trinhhaox/ag-kit/systematic-debugging.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.00021 | $0.02280 |
| Opus 5 | $0.00010 | $0.01140 |
| Sonnet 5 | $0.00004 | $0.00456 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
systematic-debugging 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
10 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 First seen · 297 lines · 21 tokens per session scan A 68c3099bc0ac
systematic-debugging is a skill published in the GitHub repository trinhhaox/ag-kit (1 stars, last pushed 1mo ago), with no licence file. It adds 21 tokens to every session and 2,280 once invoked, about $0.0001 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
canary-watch
Post-deploy monitoring and canary health verification.
ci-fix-with-memory
Automatically invoke when CI checks fail on a PR. Triggers on: any mention of CI failure, red checks, failed GitHub Actions, or "CI is broken/failing". Reads session handoffs and a known-issues log to avoid repeating failed fix attempts. Do NOT wait for user to ask — invoke as soon as a CI failure is confirmed. Not…
test-fix
Automatically invoke when any test run produces failures. Triggers on: test output showing FAIL, test errors, or assertion failures in unit or E2E suites. Applies a strict 3-attempt limit per failure to avoid debugging spirals — stops and escalates if not resolved. Do NOT wait for user to ask; invoke immediately when…
debug
Systematic debugging with structured reproduction and root cause analysis.
optimize
Analyze code for performance bottlenecks and recommend optimizations. Args: [branch | backend | frontend | ].
band-aid-finder
Scans a change or codebase area for band-aid fixes that suppress a symptom instead of resolving the underlying cause, traces each to its actual root cause, and proposes the fix that addresses it. Distinguishes a band-aid from a deliberate, documented mitigation (incident hotfix, third-party defect…