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 udapy/rust-agentic-skills --skill general-debuggit clone --depth 1 https://github.com/udapy/rust-agentic-skillsWrote 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/udapy/rust-agentic-skills/general-debug)<a href="https://agentmods.dev/skills/udapy/rust-agentic-skills/general-debug"><img src="https://agentmods.dev/badge/skills/udapy/rust-agentic-skills/general-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/udapy/rust-agentic-skills/general-debug"><img src="https://agentmods.dev/badge/skills/udapy/rust-agentic-skills/general-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.00009 | $0.00216 |
| Opus 5.5 | $0.00004 | $0.00086 |
| Sonnet 5.5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
Debug Helper 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
<role_definition> You are the Debug Helper, the detective of the Rust Guild. Your trigger: Runtime panics, logic errors, or unexpected behavior (not compiler errors). </role_definition>
- Reproduction:
- Can you write a test case that fails?
- If not, create a minimal reproducible example (MRE).
- Isolation:
- Use "Wolf Fence" debugging: Binary search the code to find the point of failure.
- Insert
dbg!()macros (better thanprintln!).
- Resolution: - Once isolated, fix the logic. - Remove all
dbg!()calls before final commit.
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 · 30 lines · 9 tokens per session scan A ac2f751f21ee
Debug Helper is a skill published in the GitHub repository udapy/rust-agentic-skills (56 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 216 once invoked, about $0.0000 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
cpp-sanitizers
Use in C/C++ projects for crashes, hangs, UB, data races, memory errors. ASan/UBSan/TSan runtime checks. Build sanitizer config separately.
rust-performance
Rust performance workflow: benchmark and profile first, identify hotspots, reduce allocations and contention, improve data layout, tune release profiles, and verify gains with repeatable evidence. Use only after you have a real Rust performance symptom, regression, or hotspot in .rs code.
gdb
Debug and trace C/C++/Rust programs with the GNU Debugger (GDB) without blocking the agent. Use when you need to set tracepoints, inspect variables, or monitor a running process while staying responsive to the user.
rust-concurrency
Use when implementing or debugging Rust threads, Send/Sync bounds, Arc and synchronization, channels, Tokio async tasks, cancellation, graceful shutdown, backpressure, deadlocks, or choosing Rayon for CPU-bound parallel work.
rust-idiomatic
Use when writing or reviewing ordinary Rust, fixing move/borrow/lifetime errors, handling Option or Result, choosing standard-library string/iterator/I/O APIs, or configuring Cargo workspaces, rustfmt, Clippy, and rust-analyzer. Covers UTF-8, partial moves, allocation semantics, and production error propagation; use…
rust-macros
Use when writing or debugging Rust macrorules! matchers, repetitions, hygiene, $crate exports, edition-dependent fragments, or procedural derive, attribute, and function-like macros using syn and quote; includes expansion and diagnostic tests.