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 PlamenTSV/plamen --skill rust-unsafe-auditgit clone --depth 1 https://github.com/PlamenTSV/plamenWrote 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/plamentsv/plamen/rust-unsafe-audit)<a href="https://agentmods.dev/skills/plamentsv/plamen/rust-unsafe-audit"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/rust-unsafe-audit/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/plamentsv/plamen/rust-unsafe-audit"><img src="https://agentmods.dev/badge/skills/plamentsv/plamen/rust-unsafe-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 192 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00039 | $0.03481 |
| Opus 5.5 | $0.00016 | $0.01392 |
| Sonnet 5.5 | $0.00008 | $0.00696 |
| Haiku 4.5 | $0.00004 | $0.00348 |
Grade A, and why
rust-unsafe-audit 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Injectable Skill: Rust Unsafe Audit
L1 trigger:
L1_PATTERN=trueAND target language = Rust Inject Into: Every L1 depth agent working on Rust code, in addition to the main skill Finding prefix:[RS-N]Status: v0.1 draft, Round 4 exemplars pending
When This Skill Activates
Supplement to the main L1 skills when the target is written in Rust. Rust's safe subset prevents most memory safety bugs by default, but node clients use unsafe for performance (crypto, serialization), panic! for unrecoverable states, and FFI (blst, rocksdb, librocksdb-sys). Each is a bug class.
1. Unsafe Block Audit
Every unsafe block is a memory-safety assertion by the author: "I guarantee this is safe." The audit must verify that guarantee.
Detection:
cargo-geigercounts unsafe per crate (cross-platform)- Ast-grep
unsafe { $$ }andunsafe fn $NAMEandunsafe impl - For each, read the surrounding safety comment (Rust convention:
// SAFETY: ...comment should justify the unsafe)
Checklist per unsafe block:
- Pointer deref: is the pointer non-null? Aligned? Pointing to valid memory of the right type and lifetime?
- Type transmutation: is the layout guaranteed? (
#[repr(C)],#[repr(transparent)]) - FFI call: are the C function's preconditions documented and met?
- Raw integer-to-pointer: is this actually sound, or just "works on current compiler"?
Tag: [RS-UNSAFE:{loc}:{category}]
2. Uninitialized Memory
Rust allows uninitialized memory via MaybeUninit or mem::uninitialized (deprecated). Reading uninitialized memory is Undefined Behavior.
Detection:
- Grep
MaybeUninit,mem::uninitialized - For each, verify the memory is initialized before
assume_init()is called MaybeUninit::zeroed()for non-zeroable types is UB
Tag: [RS-UNINIT:{loc}]
3. Send / Sync Violations
Send allows a type to be transferred between threads; Sync allows shared references across threads. Manually implementing them (unsafe impl Send for T) is an assertion.
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 · 219 lines · 39 tokens per session scan A 1ce4dde62a47
rust-unsafe-audit is a skill published in the GitHub repository PlamenTSV/plamen (308 stars, last pushed 29d ago), licensed MIT. It adds 39 tokens to every session and 3,481 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-09-03.
Other skills, from other repositories
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
prowler-ui
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
gcs-rust-download-object-api
Fix "DownloadObjectRequest not found" error in google-cloud-storage Rust crate. Use when: (1) Trying to download objects from GCS using the Rust SDK, (2) Looking for a download request type in http::objects::download module, (3) Compile error about missing type. The downloadobject method uses GetObjectRequest from the…