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 Tariux/AI-Skills-Not-Awesome --skill debugginggit clone --depth 1 https://github.com/Tariux/AI-Skills-Not-AwesomeWrote 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/tariux/ai-skills-not-awesome/debugging)<a href="https://agentmods.dev/skills/tariux/ai-skills-not-awesome/debugging"><img src="https://agentmods.dev/badge/skills/tariux/ai-skills-not-awesome/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/tariux/ai-skills-not-awesome/debugging"><img src="https://agentmods.dev/badge/skills/tariux/ai-skills-not-awesome/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.00017 | $0.00288 |
| Opus 5 | $0.00009 | $0.00144 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
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 10d 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.
- 10d ago First seen · 38 lines · 17 tokens per session scan A b0a137e5bcaf
Debugging is a skill published in the GitHub repository Tariux/AI-Skills-Not-Awesome (45 stars, last pushed 29d ago), with no licence file. It adds 17 tokens to every session and 288 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-08-30.
Other skills, from other repositories
systematic-debug
4-phase root cause analysis and debugging.
create-supervisor
Create, update, list, and safely maintain evidence-bounded graduate-advisor Skills from comments, meeting notes, chat logs, documents, and user corrections. Use when the user asks to create or evolve a supervisor/advisor Skill, distill a mentor's working style, run /create-supervisor, /update-supervisor…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…
edge-case-hunter
Focuses specifically on unusual inputs, boundary conditions, empty states, and unexpected user behavior that implementations commonly miss. Use to find what a normal test pass would skip over.
flaky-test-diagnoser
Diagnoses why a test passes sometimes and fails others - timing, shared state, ordering dependence, or external dependencies - and proposes a fix. Use when a test fails intermittently.
bug-hunter
Searches code specifically for potential bugs, edge cases, race conditions, and incorrect assumptions rather than general style/quality. Use when the goal is finding what's broken, not improving what already works.