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 subhansh-dev/agent-maxxing --skill debugging-patternsgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/subhansh-dev/agent-maxxing/debugging-patterns)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/debugging-patterns"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/debugging-patterns/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/subhansh-dev/agent-maxxing/debugging-patterns"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/debugging-patterns.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.00026 | $0.00524 |
| Opus 5.5 | $0.00010 | $0.00210 |
| Sonnet 5.5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
debugging-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Patterns — How to Fix Things
The Debugging Chain
When you hit a bug:
- Read the error message completely. All of it. Don't skim.
- Reproduce it. Run the code. Hit the error. See it yourself.
- Bisect. Comment out half the code. Does it still happen? Binary search.
- Add logging. Print the state at each step. Don't guess — measure.
- Trace the flow. Follow the data from input to output. Where does it go wrong?
- Check the obvious. Typos, wrong variable names, missing imports, stale caches.
- Search for it. Someone else probably hit this. Stack Overflow, GitHub issues, docs.
- Try the simplest fix first. Don't refactor the whole system for a typo.
- If you're going in circles, stop. Explain what you've tried and why each attempt failed.
Common Bug Categories
Null/Undefined
- Check if the value is actually defined before using it
- Trace where it comes from — is it async? Is it cached?
- Add a guard:
if (!value) returnorvalue ?? fallback
Async/Timing
- Is something racing? Add
awaitor locks - Is the order wrong? Log timestamps
- Is the callback firing twice? Check event listener cleanup
State
- Is the state stale? Log it before and after
- Is it shared between instances? Check for singleton issues
- Is it being mutated unexpectedly? Use immutable patterns
Environment
- Is it a different Node/Python version?
- Is it a different OS? (path separators, line endings)
- Is it a different environment variable?
- Is it a cached build? Clean and rebuild.
The "Rubber Duck" Technique
Explain the problem out loud (or in a comment). The act of articulating it often reveals the solution. If you can't explain it simply, you don't understand it yet.
When to Ask for Help
After you've:
- Read the error completely
- Reproduced it
- Tried the obvious fixes
- Added logging
- Searched for similar issues
- Still stuck
Then ask. Include: what you tried, what happened, what you expected.
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 · 60 lines · 26 tokens per session scan A 09b72ca9900d
debugging-patterns is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 524 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
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
smell
Detect software architecture bad smells, algorithmic complexity hotspots, and anti-patterns in a codebase. Produces a detailed markdown report identifying violations of architectural principles, design patterns, code quality, and performance complexity. Triggers on: smell, code smell, architecture smell, find…
correctness-reviewer
Always-on code-review persona. Reviews code for logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches. Spawned by the ce:review-beta skill as part of a reviewer ensemble.
performance-reviewer
Conditional code-review persona, selected when the diff touches database queries, loop-heavy data transforms, caching layers, or I/O-intensive paths. Reviews code for runtime performance and scalability issues. Spawned by the ce:review-beta skill as part of a reviewer ensemble.
reliability-reviewer
Conditional code-review persona, selected when the diff touches error handling, retries, circuit breakers, timeouts, health checks, background jobs, or async handlers. Reviews code for production reliability and failure modes. Spawned by the ce:review-beta skill as part of a reviewer ensemble.
flutter-svg-engineering
Design, implement, review, debug, test, migrate, secure, and optimize SVG rendering in production Flutter applications using fluttersvg and vectorgraphics. Use whenever a Flutter task involves SvgPicture, SVG assets, remote/dynamic SVG, SVG theming or ColorMapper, BoxFit/layout/clipping, semantics or RTL, SVG caching…