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 ankur-gaurav161418/omniforge --skill systematic-debugginggit clone --depth 1 https://github.com/ankur-gaurav161418/omniforgeWrote 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/ankur-gaurav161418/omniforge/systematic-debugging)<a href="https://agentmods.dev/skills/ankur-gaurav161418/omniforge/systematic-debugging"><img src="https://agentmods.dev/badge/skills/ankur-gaurav161418/omniforge/systematic-debugging.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.1 | $0.00020 | $0.00190 |
| Opus 5 | $0.00010 | $0.00095 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
Systematic Debugging 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 7d 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
OmniForge Systematic Debugging Skill
Purpose
Prevent superficial symptom patching by enforcing empirical hypothesis testing, full log inspection, and reproducible test cases.
Core Rules
- Log Inspection First: Never diagnose without reading complete, un-truncated error logs.
- Reproduce: Write a failing test case or reproduction script before touching application code.
- Isolate Root Cause: Trace dataflow upstream to locate the exact origin of failure.
- Fix & Verify: Apply fix, verify tests pass, ensure no regression side effects.
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.
- 7d ago First seen · 20 lines · 20 tokens per session scan A 970506735a78
Systematic Debugging is a skill published in the GitHub repository ankur-gaurav161418/omniforge (0 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 190 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
cluster-7
Skill for the Cluster7 area of bloxforge. 10 symbols across 3 files.
bug-diagnosis
Use this skill to systematically diagnose the root cause of a bug before attempting a fix. Activates when a bug is reported, a test is failing, or unexpected behavior is observed. Prevents guess-and-check debugging that introduces additional bugs while chasing symptoms.
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".