Borrowing it
Nothing to install: this file belongs to MannanSaood/termi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MannanSaood/termi/main/.cursor/skills/debug-rust-panic/SKILL.mdgit clone --depth 1 https://github.com/MannanSaood/termiWrote 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/mannansaood/termi/debug-rust-panic)<a href="https://agentmods.dev/skills/mannansaood/termi/debug-rust-panic"><img src="https://agentmods.dev/badge/skills/mannansaood/termi/debug-rust-panic/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/mannansaood/termi/debug-rust-panic"><img src="https://agentmods.dev/badge/skills/mannansaood/termi/debug-rust-panic.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.00051 | $0.00831 |
| Opus 5.5 | $0.00020 | $0.00332 |
| Sonnet 5.5 | $0.00010 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
debug-rust-panic 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this checklist whenever a cargo test run fails, a panic message
shows up in logs, or behavior doesn't match what a test expects.
1. Reproduce narrowly
cd rust
cargo test <failing_test_name> -- --nocapture
--nocapture shows println!/log output even for passing tests, which
often reveals the actual sequence of events leading to a failure that the
assertion message alone doesn't show.
2. Classify the failure
- Panic with a
.unwrap()/.expect()in the message: this should have been caught byclippy::unwrap_usedbefore it ever ran. Two possibilities:- It's in a
#[cfg(test)] mod testsblock — expected, not a bug, unless the test itself is wrong. - It's in production code — this is a regression in lint coverage.
Check whether the file has
#![warn(clippy::unwrap_used)]inherited fromlib.rs(it should, crate-wide) and whether clippy was actually run before this code was merged (cargo clippy --all-targets -- -D warnings -D clippy::unwrap_used -D clippy::expect_used).
- It's in a
- Poisoned mutex panic (
PoisonErroror "lock" in the message): check whether the code uses.lock().unwrap()instead ofutils::sync_ext::LockExt::lock_safe(). If it's a data buffer (not a mutex protecting a real invariant), switch tolock_safe()— see that module's doc comment for when this is/isn't appropriate. - VFS operation failed unexpectedly: check whether the code called a
FsProvidermethod directly instead of going throughVfsService. If it went throughVfsService, check whether theVfsOutcomewasBlocked(capability check failed — expected for chmod/symlink on SAF) vs. an actual bug. Readvfs/capabilities.rs's capability matrix for the relevantFsTypebefore assuming it's a bug. - JNI-related failure: this can only be meaningfully debugged
on-device or with device logs (
adb logcat). Don't try to reproduce JNI crashes withcargo test— theandroidfeature only type-checks on host, it doesn't give you a JVM to actually exercise those code paths.
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 · 73 lines · 51 tokens per session scan A 7d539c8b8678
debug-rust-panic is a skill published in the GitHub repository MannanSaood/termi (10 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 831 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-31.
Other skills, from other repositories
cranpose
Cranpose UI framework conventions, APIs, and patterns. Use when writing Cranpose composables, state, layout, or modifiers, or when working in a project that depends on the cranpose crates.
kmp-architecture-footguns
Kotlin Multiplatform structure and language traps: module splits, expect/actual, Koin and ViewModel scoping, layers, version catalogs, erased overloads, Char and string-resource formatting limits. Use when shaping modules or DI, when a format specifier renders verbatim, or code misbehaves on one platform.
state-and-background-footguns
Reactive state and background-work traps: StateFlow conflation, flatMapLatest, job lifecycles, ViewModel bases, WorkManager, backups, crash reporting, logging, Glance widgets. Use when state lags or flips, or work runs twice or never.
go-rust-reverse
Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.
rust-check
Run cargo check on the current Rust project to find compile errors.
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.