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 roedyrustam/vibes-plug --skill secure-fuzz-testinggit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/secure-fuzz-testing)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/secure-fuzz-testing"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/secure-fuzz-testing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.02173 |
| Opus 5 | $0.00016 | $0.01086 |
| Sonnet 5 | $0.00007 | $0.00435 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
secure-fuzz-testing 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 4d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure Fuzz Testing
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
Expert-level guidance for writing, running, and integrating coverage-guided fuzz tests (fuzzing) to identify security vulnerabilities, memory leaks, and input-validation issues in software applications. This skill covers writing fuzz targets in Python, Rust, and Go, configuring compilers with sanitizers (ASan, MSan, UBSan), and setting up automated CI/CD security pipelines.
Trigger Conditions
- Use when designing or reviewing data parsers, serialization/deserialization logic, or file formats.
- Use when writing libraries that process untrusted network input or binary data streams.
- Use when integrating automated security testing into a DevSecOps pipeline (CI/CD).
- Use when troubleshooting complex memory bugs, edge-case crashes, or unhandled exceptions.
Writing Fuzz Targets
Coverage-guided fuzzers need a target function that accepts a stream of bytes and processes it.
1. Python Fuzzing (Atheris)
Atheris is a coverage-guided fuzzer for Python. It can fuzz Python code and native extensions:
import sys
import atheris
with atheris.instrument_imports():
import our_parser # Import target module inside instrument_imports
def TestOneInput(data):
if len(data) < 4:
return
try:
# Decode and parse the byte data
text = data.decode("utf-8", errors="ignore")
our_parser.parse_config(text)
except our_parser.ParseException:
# Expected exceptions should be caught to avoid false positives
pass
atheris.Setup(sys.argv, TestOneInput)
atheris.Fuzz()
2. Rust Fuzzing (cargo-fuzz & libFuzzer)
Rust has first-class fuzzing support via cargo-fuzz which wraps libFuzzer:
#![no_main]
use libfuzzer_sys::fuzz_target;
fuzz_target!(|data: &[u8]| {
if let Ok(input_str) = std::str::from_utf8(data) {
let _ = our_crate::parse_config(input_str);
}
});
- Run Fuzzer: Execute
cargo +nightly fuzz run <target_name>.
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.
- 4d ago First seen · 208 lines · 33 tokens per session scan A e2a64ebe1592
secure-fuzz-testing is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,173 once invoked, about $0.0002 per session on Opus 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
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…
exploratory-test
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than /smoke-test. Use when the user asks to "exploratory test", "test…
create-test-plan
Analyze what changed and generate a structured test plan at .turbo/test-plans/ .md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios"…
quick-finalize
Close out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the…