Borrowing it
Nothing to install: this file belongs to future-architect/uzomuzo-oss. 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/future-architect/uzomuzo-oss/main/.claude/skills/diet-fuzz/SKILL.mdgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/future-architect/uzomuzo-oss/diet-fuzz)<a href="https://agentmods.dev/skills/future-architect/uzomuzo-oss/diet-fuzz"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/diet-fuzz/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/future-architect/uzomuzo-oss/diet-fuzz"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/diet-fuzz.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00569 |
| Opus 5 | $0.00028 | $0.00284 |
| Sonnet 5 | $0.00011 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
diet-fuzz 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 9d 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
/diet-fuzz — Batch Diet Fuzz Testing
Full specification: See
.github/prompts/diet-fuzz.prompt.mdfor the complete execution pipeline, project selection algorithm, and issue filing format.
Quick Reference
- Full run:
/diet-fuzz all— 5 projects × 4 languages × 3 SBOM tools - Targeted:
/diet-fuzz go,typescript --count 10— 10 projects × 2 languages - Single tool:
/diet-fuzz python --tool syft --count 3 - Curated:
/diet-fuzz all --projects-file projects.txt - High parallel:
/diet-fuzz all --max-parallel 8
Pipeline
- Pull
origin/main& rebuilduzomuzo-diet - Select projects (stratified sampling or projects-file)
- Pre-filter (clone + SBOM, skip empty dependency graphs)
- Run
uzomuzo-dietper project × tool - Detect anomalies (IBNC, EOL-ZERO-SCORE, HIGH-SCORE-BUT-HARD)
- Compare with previous runs (auto-diff)
- Auto-file/update GitHub issues (grouped by root cause)
- Append new findings to
uzomuzo-diet-findings.md - Display cross-language summary table
Key Points
- Stratified sampling: Projects chosen across popularity tiers (stars) and time periods for parser pattern diversity
- All SBOM tools by default: trivy, syft, cdxgen — cross-tool comparison reveals tool-specific issues
- Auto issue management: Creates new issues or adds evidence to existing ones, labels
bug+diet-trial+lang:* - Regression detection: Compares with past runs to catch accuracy regressions
- Pre-filter: Skips projects where SBOM has no dependency graph (avoids wasted diet runs)
- Uses
gh api(REST) for GitHub operations to avoid GraphQL rate limits
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.
- 9d ago First seen · 45 lines · 56 tokens per session scan A 722c2fd7b231
diet-fuzz is a skill published in the GitHub repository future-architect/uzomuzo-oss (32 stars, last pushed 3d ago), licensed Apache-2.0. It adds 56 tokens to every session and 569 once invoked, about $0.0003 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-01.
Other skills, from other repositories
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
test-fix
Diagnose and minimally fix a failing test, then re-run.