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/subhansh-dev/agent-maxxing/debugging-patternsnpx skills add subhansh-dev/agent-maxxing --skill debugging-patternsgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWhat 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.00026 | $0.00524 |
| Opus 5 | $0.00013 | $0.00262 |
| Sonnet 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 yesterday.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 26 tokens to every session and 524 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-31.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…