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 Master0fFate/parallax-claudecode --skill debuggit clone --depth 1 https://github.com/Master0fFate/parallax-claudecodeWrote 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/master0ffate/parallax-claudecode/debug)<a href="https://agentmods.dev/skills/master0ffate/parallax-claudecode/debug"><img src="https://agentmods.dev/badge/skills/master0ffate/parallax-claudecode/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/master0ffate/parallax-claudecode/debug"><img src="https://agentmods.dev/badge/skills/master0ffate/parallax-claudecode/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.00018 | $0.00215 |
| Opus 5.5 | $0.00007 | $0.00086 |
| Sonnet 5.5 | $0.00004 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
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
Debug
Pass the current Claude session ID to parallax_debug. Audit $ARGUMENTS with professional skepticism.
- Establish the expected behavior and reproduce the symptom with the narrowest reliable command.
- Separate direct evidence, strong inference, and unknowns. Trace state ownership, feedback, coupling, and timing before proposing a cause.
- Rank findings by material impact and likelihood. Cite paths, tests, logs, or command output; ignore cosmetic noise unless requested.
- Fix root causes rather than suppressing errors. Keep the patch surgical and add a regression check that fails before the fix when practical.
- Run targeted verification, then broader checks proportional to blast radius.
Report diagnosis, root cause, changed files, test evidence, limitations, and remaining risk. If evidence is insufficient, say so rather than assigning a confident verdict.
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 · 19 lines · 18 tokens per session scan A 14e9a54213f8
debug is a skill published in the GitHub repository Master0fFate/parallax-claudecode (0 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 215 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
systematic-debugging
Root-cause-first debugging discipline — build a red-capable feedback loop, minimise the repro, rank falsifiable hypotheses, fix at the source.
error-handling-patterns
Error handling patterns across languages — exceptions, Result types, propagation, graceful degradation.
ci-routing
The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the single-render rule, and the fix-then-re-watch loop.
postmortem-writing
Author blameless incident postmortems — timeline, root cause(s), contributing factors, action items.
postgresql-optimization
Write or review PostgreSQL-specific SQL: JSONB, arrays, custom/range/geometric types, indexing, full-text search, window functions, extensions, and RLS.
sentry-cli
Guide for using the Sentry CLI from the command line.