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 AyushParkara/syntra --skill systematic-debuggit clone --depth 1 https://github.com/AyushParkara/syntraWrote 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/ayushparkara/syntra/systematic-debug)<a href="https://agentmods.dev/skills/ayushparkara/syntra/systematic-debug"><img src="https://agentmods.dev/badge/skills/ayushparkara/syntra/systematic-debug/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/ayushparkara/syntra/systematic-debug"><img src="https://agentmods.dev/badge/skills/ayushparkara/syntra/systematic-debug.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.00037 | $0.00302 |
| Opus 5.5 | $0.00015 | $0.00121 |
| Sonnet 5.5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
systematic-debug 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.
What it actually says
You debug systematically in 4 phases. No guessing, no shotgun fixes.
Phase 1 — REPRODUCE:
- Establish the exact conditions that trigger the bug. Get the error, stack trace, or precise wrong behavior. If you can't reproduce it, you can't fix it — say so and propose how to capture more evidence.
Phase 2 — ISOLATE:
- Narrow to the smallest code path that exhibits the bug. Bisect: comment out, add logging, or binary-search the input. Form ONE hypothesis at a time and test it before moving on. Trace the actual data flow — don't assume.
Phase 3 — FIX THE ROOT CAUSE:
- Once the true cause is confirmed (not a symptom), apply the smallest change that addresses it. A patch that hides the error is worse than none.
Phase 4 — VERIFY:
- Confirm the original reproduction no longer triggers the bug.
- Check you didn't break adjacent behavior (run the tests).
- Note what the fix does NOT cover.
Rules:
- State your current phase as you work.
- One hypothesis at a time; confirm before fixing.
- Never claim "fixed" without re-running the reproduction.
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 · 32 lines · 37 tokens per session scan A 66aed058d2f5
systematic-debug is a skill published in the GitHub repository AyushParkara/syntra (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 302 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
optimization
Use when improving performance, latency, throughput, memory usage, or general efficiency. Start by defining target metrics, measuring comprehensively, attributing bottlenecks, validating with static analysis, and prioritizing macro-optimizations before micro-optimizations.
pi-observability-local-dev
Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.