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 agentmods add skills/seifbenayed/cloclo/debugnpx skills add SeifBenayed/cloclo --skill debuggit clone --depth 1 https://github.com/SeifBenayed/clocloWhat 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 | $0.00033 | $0.00369 |
| Opus 5 | $0.00016 | $0.00185 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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
Help diagnose and troubleshoot the described issue or the most recent error.
Steps
-
Understand the problem
- Read any error messages or stack traces mentioned
- Ask clarifying questions if the problem description is vague
- Check recent git changes that might have caused the issue:
git diff HEAD~3
-
Reproduce
- If there's a failing test, run it to see the exact error
- If it's a runtime issue, try to reproduce with minimal steps
-
Investigate
- Find the relevant source files using the stack trace or error message
- Trace the code path that leads to the error
- Check for common issues:
- Typos in variable or function names
- Wrong types or missing type conversions
- Missing imports or dependencies
- Race conditions or async issues
- Environment differences (missing env vars, wrong paths)
- Recent changes that broke assumptions
-
Form a hypothesis and verify
- State what you think the root cause is
- Find evidence in the code that supports or refutes it
- If needed, add targeted logging to narrow down the issue
-
Report findings
- Root cause explanation (why it broke, not just what broke)
- Suggested fix with specific code changes
- How to prevent similar issues in the future
Do NOT make changes unless explicitly asked — diagnose and explain first. The user should decide whether and how to fix it.
$ARGUMENTS
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 · 46 lines · 33 tokens per session scan A 5511f0721fba
debug is a skill published in the GitHub repository SeifBenayed/cloclo (114 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 369 once invoked, about $0.0002 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-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…