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 MRWillisT/PullNexus --skill systematic-debugginggit clone --depth 1 https://github.com/MRWillisT/PullNexusWrote 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/mrwillist/pullnexus/systematic-debugging)<a href="https://agentmods.dev/skills/mrwillist/pullnexus/systematic-debugging"><img src="https://agentmods.dev/badge/skills/mrwillist/pullnexus/systematic-debugging/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/mrwillist/pullnexus/systematic-debugging"><img src="https://agentmods.dev/badge/skills/mrwillist/pullnexus/systematic-debugging.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.00021 | $0.02299 |
| Opus 5.5 | $0.00008 | $0.00920 |
| Sonnet 5.5 | $0.00004 | $0.00460 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
systematic-debugging 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
3 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 · 298 lines · 21 tokens per session scan A d0e3689f7075
systematic-debugging is a skill published in the GitHub repository MRWillisT/PullNexus (7 stars, last pushed 5mo ago), with no licence file. It adds 21 tokens to every session and 2,299 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
code-review
Performs structured code review on a file or directory.
self-map
Your evidence and how you work: one Trace turn to its cause and whose it is (owner side, the Version, outside); spend, schedules, failures, the journal, docs; what Stop, Interrupt or a break leave; where to look before asking. Load in an Insight turn with failures, when the owner asks what you did, why it failed, what…
report-problem
A troubleshooting procedure for a broken Iva assistant, schedule, tool, or delivery. It collects a diagnostic report, checks recent logs and facts, and prepares either an issue report or a support-chat message.
review-rfc
Review an implemented RFC in a fresh context against its acceptance criteria, RULES.md and the test plan, and save the review to reviews/.
offensive-crash-analysis
Week 4 exploit development curriculum. Crash triage and analysis methodology: WinDbg/GDB analysis, ASAN/MSAN output interpretation, exploitability assessment, register/stack trace reading, root cause identification. Use when analyzing crash dumps, assessing exploitability, or understanding fuzzer-generated crashes.
regex
Write, test, and debug regular expressions for pattern matching, search, and text extraction across programming languages. Use when the user asks to match patterns in text, validate input formats (email, URL, IP, phone, date), extract data with capture groups, build search patterns with lookahead or lookbehind, or…