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 johnqtcg/awesome-skills --skill fuzzing-testgit clone --depth 1 https://github.com/johnqtcg/awesome-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/johnqtcg/awesome-skills/fuzzing-test)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/fuzzing-test"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/fuzzing-test/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/johnqtcg/awesome-skills/fuzzing-test"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/fuzzing-test.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 analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00074 | $0.04878 |
| Opus 5 | $0.00037 | $0.02439 |
| Sonnet 5 | $0.00015 | $0.00976 |
| Haiku 4.5 | $0.00007 | $0.00488 |
Grade A, and why
fuzzing-test 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 10d 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 — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fuzzing Test Skill (Go)
Generate high-signal Go fuzz tests only when targets are suitable.
Quick Reference — Load References Selectively
Read the section named below first; load the reference only when its trigger applies.
| When you need to… | Section | Load on demand |
|---|---|---|
| Decide if a target is suitable | §Applicability Gate (run first, always) | applicability-checklist.md — full decision tree, oracle forms, version gate, borderline cases |
| Choose among 3+ candidate targets | §Target Priority Gate | target-priority.md — bug-yield ranking and tie-breaks |
| Write the harness | §Minimal Templates | — |
| Handle a discovered crash | §Crash Handling | crash-handling.md — triage steps, corpus policy, report template |
| Set up CI | §CI Strategy | ci-strategy.md — Actions config, corpus caching, budgets |
| Diagnose a slow/ineffective run, OOM, leak, or flake | §Fuzz Performance Baseline | advanced-tuning.md — seed quality, skip-rate, allocation profiling |
| Avoid or check for common mistakes | §Quality Scorecard | anti-examples.md — 9 BAD/GOOD harness patterns |
Applicability Gate (Must Run First)
Before writing any fuzz code, evaluate suitability. If the target fails this gate, the entire remaining workflow is skipped — output the verdict, suggest alternatives, and stop.
Mark each item Pass / Fail:
- Target has meaningful input space (not trivial fixed-path logic).
- Target can be driven by Go fuzz-supported parameter types.
- Target has clear oracle/invariant:
- no panic for any input
- round-trip (
decode(encode(x)) == x) - differential consistency
- domain constraints/properties
- Target is mostly deterministic/local (not dominated by DB/network/clock/global mutable state).
- Target is fast enough for high-iteration fuzzing.
Hard stop — items 1, 2, and 3 are each independently blocking:
| Failed item | Why it stops the workflow |
|---|---|
1 meaningful input space |
Fuzzing adds nothing a table-driven unit test would not find |
2 fuzz-supported types |
Go's fuzzer cannot drive the target at all |
3 clear oracle |
No way to recognise a bug even when the input triggers it |
What ships with it
36 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.
- references/advanced-tuning.md 6.3 KB
- references/anti-examples.md 4.0 KB
- references/applicability-checklist.md 8.6 KB
- references/ci-strategy.md 7.6 KB
- references/crash-handling.md 2.0 KB
- references/target-priority.md 6.0 KB
- scripts/run_regression.sh 604 B runs code
- scripts/tests/COVERAGE.md 15 KB
- scripts/tests/golden/001_parser_suitable.json 761 B
- scripts/tests/golden/002_roundtrip_suitable.json 775 B
- scripts/tests/golden/003_differential_suitable.json 753 B
- scripts/tests/golden/004_struct_aware_suitable.json 774 B
- scripts/tests/golden/005_trivial_not_suitable.json 680 B
- scripts/tests/golden/006_no_oracle_not_suitable.json 752 B
- scripts/tests/golden/007_db_dependent_not_suitable.json 785 B
- scripts/tests/golden/008_validator_with_race.json 787 B
- scripts/tests/golden/009_crash_handling_workflow.json 815 B
- scripts/tests/golden/010_ci_integration_workflow.json 692 B
- scripts/tests/golden/011_borderline_soft_warning.json 1.0 KB
- scripts/tests/golden/012_go_fuzz_headers_suitable.json 685 B
- scripts/tests/golden/013_go_directive_low_toolchain_modern.json 1.5 KB
- scripts/tests/golden/014_corpus_management_degradation.json 1.6 KB
- scripts/tests/golden/015_toolchain_below_118_hard_stop.json 1.3 KB
- scripts/tests/llm_eval/frame_parser/bad.md 528 B
- scripts/tests/llm_eval/frame_parser/good.md 3.5 KB
- scripts/tests/llm_eval/frame_parser/meta.json 918 B
- scripts/tests/llm_eval/frame_parser/README.md 3.3 KB
- scripts/tests/llm_eval/frame_parser/sut.go 779 B
- scripts/tests/llm_eval/kv_codec/bad.md 632 B
- scripts/tests/llm_eval/kv_codec/good.md 3.6 KB
- scripts/tests/llm_eval/kv_codec/meta.json 1.1 KB
- scripts/tests/llm_eval/kv_codec/sut.go 1.1 KB
- scripts/tests/test_golden_scenarios.py 14 KB runs code
- scripts/tests/test_llm_fuzz_eval.py 20 KB runs code
- scripts/tests/test_skill_contract.py 18 KB runs code
- scripts/tests/test_templates_compile.py 7.1 KB runs code
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.
- 10d ago First seen · 485 lines · 74 tokens per session scan A f8e0bae854af
fuzzing-test is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 4,878 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
ci-tests
Run the test suite for the current repo, auto-detecting Python (pytest/uv), Node (vitest/pnpm), or Rust (cargo test).