Menu
Use when writing or contributing a boofuzz network-protocol fuzzer in this repo — layout, formatting rules, and reading results.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Anthropic API rate limit handling - retry logic, backoff, throttling for batch workloads against Claude models
Use when building an automated test → issue → fix loop with Claude Code and GitHub issues — overnight auto-fixing, regression loops, self-healing CI.
Use when creating, editing, publishing, or deleting posts on Cyril's Workshop blog or the steponnopets.net devblog.
Use when a task needs real-time control of a connected browser via the Browser Bridge Broker — submit JS jobs over HTTP that browsers eval and return.
Use when training a character LoRA (Chroma/Flux or Pony/SDXL) on a RunPod GPU and wiring it into the ComfyUI + pony_web render stack.
Use when writing a new skill or revising an existing one — format, trigger descriptions, and what content belongs in a skill.
| name | boofuzz |
| description | Use when writing or contributing a boofuzz network-protocol fuzzer in this repo — layout, formatting rules, and reading results. |
Conventions for authoring fuzzers in this boofuzz project. General boofuzz API usage (Request/Block/primitives, Session setup, callbacks) is standard — see the boofuzz docs.
| Directory | Contents |
|---|---|
/examples/ | Complete runnable fuzzers with a CLI (argparse, a main()). New standalone fuzzers go here. |
/request_definitions/ | Reusable protocol PDU definitions only — importable modules, no main(). |
Put a fuzzer's protocol structure in /request_definitions/ when it's worth reusing, and the runnable driver in /examples/.
Format with Black before committing; run the full checks with tox:
black your_fuzzer.py
tox
Use # fmt: off / # fmt: on sparingly — only to preserve hand-aligned protocol byte layouts that Black would reflow.
Runs land in ./boofuzz-results/*.db (SQLite). Inspect via the web UI:
boo open boofuzz-results/run-YYYY-MM-DD_HH-MM-SS.db
Or query directly, e.g. failing/crashing cases:
SELECT name, type, timestamp FROM cases
WHERE type LIKE '%fail%' OR type LIKE '%crash%';
For vulnerability disclosure templates and PoC extraction from a crash, see references/disclosure.md.