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 Razaib-khan/ForgeWeave --skill debuggergit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/razaib-khan/forgeweave/debugger)<a href="https://agentmods.dev/skills/razaib-khan/forgeweave/debugger"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/debugger/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/razaib-khan/forgeweave/debugger"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/debugger.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.00020 | $0.00656 |
| Opus 5.5 | $0.00008 | $0.00262 |
| Sonnet 5.5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
Debugger 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger
Purpose
Apply systematic debugging methodology to identify root causes of software issues. Uses hypothesis-driven investigation, binary search on code paths, and targeted tests to isolate the problem before proposing a fix.
When to Use
- The user reports a bug, error, or unexpected behavior
- A test is failing and the cause is not obvious
- A feature works locally but fails in production
- Performance regression needs investigation
When Not to Use
- The error message is self-explanatory — fix it directly
- The fix is already known and just needs implementation
- The task is refactoring — use
refactor-engine
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
symptom |
string | Yes | The observed error or unexpected behavior |
reproduction_steps |
string | No | Steps to reproduce the issue |
environment |
string | No | Environment details (OS, versions, deployment) |
logs_or_stacktrace |
string | No | Error output, logs, or stack trace |
Expected Outputs
| Output | Description |
|---|---|
| Root cause | Identified source of the issue |
| Fix strategy | Minimal change to fix the issue |
| Verification steps | How to confirm the fix works |
| Prevention | How to avoid similar issues |
Exact Workflow Steps
- Understand the symptom and reproduction steps
- Formulate 2-3 hypotheses for root cause
- For each hypothesis, design a diagnostic test
- Narrow down by eliminating hypotheses
- Isolate the exact root cause
- Design minimal fix that doesn't break other functionality
- Verify fix resolves the symptom
- Run existing tests to confirm no regressions
Required Checks
- Root cause is identified before any fix is proposed
- Fix is minimal (no scope creep)
- Existing tests pass after fix
- Prevention strategy is documented
Failure Modes
| Failure Condition | Response |
|---|---|
| Cannot reproduce the issue | Ask for more detailed reproduction steps |
| All hypotheses eliminated | Broaden search to adjacent systems or dependencies |
| Fix breaks other functionality | Revert and explore alternative fix strategy |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 94 lines · 20 tokens per session scan A d7ba65d606f7
Debugger is a skill published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 656 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
troubleshooting
A troubleshooting guide for Kubernetes, a system for running containerized applications across computers. It lists commands for checking clusters, nodes, components, pods, events, resources, and storage.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
huawei-cloud-cdn-abnormal-status-code-analysis
Diagnose CDN business abnormal HTTP status codes (4xx/5xx) using hcloud CLI. Discover and quantify 4xx/5xx volume, localize the exact status code and time window, fork edge-generated vs origin-generated via back-to-source status statistics, correlate top-N distribution, narrow root cause on CDN edge config or origin…
auto-fix
A bug-fixing workflow that first reproduces a problem with a test, then applies the smallest code change needed. It also checks the related code path and runs tests afterward.
audit-reliability
Skill "audit-reliability" from dhaupin/vant, covering reliability, the question, what to check, 1. graceful degradation and 2. recovery.
review-efficiency
Skill "review-efficiency" from dhaupin/vant, covering efficiency review, the question, what to check, 1. compute and 2. network.