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/omnigentx/jarvis/debugging-strategiesnpx skills add omnigentx/jarvis --skill debugging-strategiesgit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/debugging-strategies)<a href="https://agentmods.dev/skills/omnigentx/jarvis/debugging-strategies"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/debugging-strategies.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00380 |
| Opus 5 | $0.00018 | $0.00190 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
debugging-strategies 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 5d 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
SYSTEMATIC DEBUGGING
4-phase process
Phase 1: REPRODUCE
- Confirm the bug exists.
- Record the exact steps to reproduce.
- Capture: error message, stack trace, logs.
Phase 2: HYPOTHESIZE
- Read the error message carefully — it usually contains a clue.
- List 2–3 of the most likely hypotheses.
- Rank them by likelihood.
Phase 3: TEST
- Test the highest-likelihood hypothesis FIRST.
- Binary search: split the code in half, test each half.
- Add temporary logging at suspect points.
- DO NOT change code before you understand the root cause.
Phase 4: FIX & VERIFY
- Fix the root cause, NOT the symptom.
- Write a test that reproduces the bug BEFORE the fix.
- Verify the fix: the new test must pass.
- Remove temporary logging.
Decision tree
What kind of bug?
├── Runtime error → Read the stack trace; locate the failing line.
├── Logic error → Add print/log at input and output points.
├── Performance → Profile: measure time spent per phase.
├── Intermittent → Look for race conditions; check timing.
└── Hard to reproduce → Add defensive logging.
❌ Anti-patterns
- Guess → patch random code → hope it works.
- Fix the symptom → root cause stays → bug returns.
- Skip writing a test → same bug recurs after a future refactor.
✅ Standard
- Reproduce → Hypothesis → Test → Fix → Verify → Commit with test.
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.
- 5d ago First seen · 53 lines · 36 tokens per session scan A 9ecc313d5c49
debugging-strategies is a skill published in the GitHub repository omnigentx/jarvis (36 stars, last pushed 9d ago), licensed MIT. It adds 36 tokens to every session and 380 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…