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 luisabwk/kraken --skill systematic-debugginggit clone --depth 1 https://github.com/luisabwk/krakenWrote 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/luisabwk/kraken/systematic-debugging)<a href="https://agentmods.dev/skills/luisabwk/kraken/systematic-debugging"><img src="https://agentmods.dev/badge/skills/luisabwk/kraken/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/luisabwk/kraken/systematic-debugging"><img src="https://agentmods.dev/badge/skills/luisabwk/kraken/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.00018 | $0.01747 |
| Opus 5.5 | $0.00007 | $0.00699 |
| Sonnet 5.5 | $0.00004 | $0.00349 |
| Haiku 4.5 | $0.00002 | $0.00175 |
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 1mo 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 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.
- 1mo ago First seen · 241 lines · 18 tokens per session scan A b1081c894d11
systematic-debugging is a skill published in the GitHub repository luisabwk/kraken (1 stars, last pushed 7mo ago), with no licence file. It adds 18 tokens to every session and 1,747 once invoked, about $0.0001 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-31.
Other skills, from other repositories
housekeep-dead-code
Remove dead code by category — one commit each, typecheck and tests between, bisect on red — then add a Knip ratchet. Use when "delete the dead code", "remove unused files", or "wire up Knip". Audit first → plan-dead-code. README/deps → workflow-housekeep.
plan-dead-code
Configuration-first dead-code audit — Knip baseline for unused files, exports and deps, plus duplication, debug residue, suppression debt, orphan assets, env and schema drift. Emits a ratchet plan; deletes nothing. Use when "find dead code", "is this code used", "unused exports". Apply → housekeep-dead-code.
audit-performance
Audit and fix runtime performance (Core Web Vitals, load priority). Use when "slow page", "LCP/INP/CLS", "fetchpriority", "long tasks", or "bfcache". JS payload → audit-bundle-size. Instant nav → enhance-web-instant-nav. Load limits → test-load.
debug-fe-be-integration
Diagnose and fix frontend↔backend contract failures by tracing requests, server logs, validation, auth, and responses on both sides. Use for API 4xx/5xx, mismatched payloads, or "frontend and backend disagree". One layer → debug-error.
debug-sentry-monitor
Operate Sentry: triage and fix unresolved issues, cut noise, audit instrumentation, monitor after deploy. Use when "check Sentry", "review production errors", or "improve error tracking". One bug → workflow-fix-and-ship. Plan-only audit → plan-error-handling.
backend-db-performance
Optimize slow queries, indexes, and N+1s. Use when "slow query", "database performance", "add an index", or "N+1". Schema consistency → audit-db-schema. RLS access control → plan-rls-audit.