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 alphacornutum/layercake --skill debuggit clone --depth 1 https://github.com/alphacornutum/layercakeWrote 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/alphacornutum/layercake/debug)<a href="https://agentmods.dev/skills/alphacornutum/layercake/debug"><img src="https://agentmods.dev/badge/skills/alphacornutum/layercake/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/alphacornutum/layercake/debug"><img src="https://agentmods.dev/badge/skills/alphacornutum/layercake/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.00109 | $0.00444 |
| Opus 5.5 | $0.00044 | $0.00178 |
| Sonnet 5.5 | $0.00022 | $0.00089 |
| Haiku 4.5 | $0.00011 | $0.00044 |
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 20d 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
Systematically find and fix the root cause of a bug.
Steps
- Reproduce — Get the exact error message, stack trace, or steps to reproduce. Understand what happens vs. what should happen.
- Locate — Narrow down where the problem is:
- Read the error message and stack trace — they usually point to the exact location.
- Search for relevant keywords (error strings, function names).
- Trace the data flow from input to the failure point.
- Understand — Before fixing, understand why it fails:
- What assumption is violated?
- When was it introduced? (
git log,git blame) - Logic error? Data problem? Race condition? Missing edge case?
- Fix — Make the smallest change that correctly addresses the root cause.
- Verify — Write or update a test that catches this bug. Run the full test suite for regressions.
- Explain — Briefly describe what caused it and why the fix is correct.
Gotchas
- Let the error surface until you understand it. A silent try-catch hides the cause and breeds a worse bug later.
- Trace to the root cause before applying the fix. Symptom-level patches return as new bugs.
- Form a hypothesis grounded in the data before changing code. Speculation burns more time than diagnosis.
- Change one thing at a time so you can tell what fixed the bug.
- Trace upstream from the error site. The bug usually lives where the bad value is produced, not where it explodes.
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.
- 20d ago First seen · 32 lines · 109 tokens per session scan A 1e50f261efd1
debug is a skill published in the GitHub repository alphacornutum/layercake (0 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 444 once invoked, about $0.0004 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-09-26.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart. Do not use for ordinary review, style feedback, or general improvement suggestions.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.