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/ayushparkara/syntra/systematic-debugnpx 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.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.00037 | $0.00302 |
| Opus 5 | $0.00018 | $0.00151 |
| Sonnet 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 4d 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.
- 4d 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 23d ago), licensed Apache-2.0. It adds 37 tokens to every session and 302 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-31.
Other skills, from other repositories
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.
ship-and-babysit
End-to-end PR shipping workflow for tinyhumansai/openhuman: commit local changes, push to the user's fork, open or reuse a PR against main, then babysit CI and CodeRabbit feedback until the PR is green and clean. Use when the user asks to ship, open a PR, monitor CI, address review comments, or 'babysit' a branch.
adr-skill
Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses…
add-harness-package
Guide for adding new AI SDK harness packages. Use when creating a new @ai-sdk/harness- package that adapts a coding-agent runtime to HarnessV1.
add-provider-package
Guide for adding first-party AI provider packages to the AI SDK. Use when creating a provider package under packages/ to integrate an external AI service.
update-provider-models
Add new or remove obsolete model IDs for existing AI SDK providers. Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue. Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs".