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 Zfinix/aster --skill debug-systematicallygit clone --depth 1 https://github.com/Zfinix/asterWrote 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/zfinix/aster/debug-systematically)<a href="https://agentmods.dev/skills/zfinix/aster/debug-systematically"><img src="https://agentmods.dev/badge/skills/zfinix/aster/debug-systematically/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/zfinix/aster/debug-systematically"><img src="https://agentmods.dev/badge/skills/zfinix/aster/debug-systematically.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00334 |
| Opus 5.5 | $0.00018 | $0.00134 |
| Sonnet 5.5 | $0.00009 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
debug-systematically 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
Debug systematically
- Reproduce before touching anything. Find the exact command or input that shows the failure and run it. A bug you cannot reproduce is a bug you cannot claim to have fixed.
- Read the actual error, not the vibe of it. The message, the file, the line. Half of debugging is refusing to skim.
- One hypothesis at a time. State it ("the config is read before the env is set"), pick the cheapest observation that would falsify it, run that. Never stack three speculative fixes in one edit.
- Instrument close to the failure. A print or assert at the suspect line beats re-reading the whole module. Remove the instrumentation after.
- Bisect when lost. Halve the search space: does the failure survive
with half the input, the previous commit, the feature flag off?
git bisectexists for exactly this. - When the fix lands, explain the mechanism in one sentence. "The cache key ignored the locale, so the first locale won." If you cannot say it, you patched a symptom.
- Re-run the original reproduction last. The fix is proven by the same command that showed the bug, plus the neighboring tests.
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 · 26 lines · 46 tokens per session scan A f7bf6b576242
debug-systematically is a skill published in the GitHub repository Zfinix/aster (129 stars, last pushed 8d ago), licensed Apache-2.0. It adds 46 tokens to every session and 334 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ctx
Codebase intelligence and evidence-driven governance with the indexed ctx CLI. Use when exploring an unfamiliar repository, locating symbols or callers, checking for existing implementations, estimating change impact, enforcing architecture rules, scoring a branch, finding hotspots or duplication, or analyzing…
node-notready-triage
Use when nodes are NotReady or the whole cluster looks unhealthy — inspects node conditions, CNI/kube-system pods, and capacity to find what is keeping the kubelet or network from being ready.
pod-crashloop-triage
Use when pods are in CrashLoopBackOff, ImagePullBackOff, ErrImagePull, or OOMKilled — collects describe/logs/events and identifies the failure class before recommending a fix.
platform-sre-triage
Use when triaging platform reliability issues — orchestrates service health reporting, then Docker disk diagnostics, then the smallest safe next action.
ml-training-job-triage
Use when triaging failed, slow, or expensive ML training jobs, GPU utilization, data/input errors, checkpoints, and retry strategy.
speccrew-test-runner
SpecCrew Test Runner. Executes test code, parses results, and detects deviations between expected and actual outcomes. Reads test code files and system design to run platform-specific test suites.