Hi wallbreaker maintainers and contributors,
I’ve built and maintain an unofficial documentation site for wallbreaker: https://wallbreaker-docs.vercel.app (source: https://github.com/ra-co88/wallbreaker-docs, Nextra/Next.js, deployed on Vercel).
The site covers what the in-repo docs don’t yet: a Getting Started path, Concept pages (agent loop, engagement model, sessions & findings), Guides (payloads, personas, campaigns, multimodal, scripting/CI, troubleshooting), full Reference (all 51 presets, 71 transforms, 100+ tools with parameters verified against the code, CLI reference, MCP server), and Policy pages (methodology, security, responsible use). Every command, config block, and parameter was fact-checked against the codebase rather than generated and trusted.
The site is live and I’ll keep maintaining it either way — but since it’s the team’s project, I wanted to put it on the team’s radar and offer options, in whatever direction you prefer:
Link it — a line in the README (“community docs”) is all it takes; I keep hosting and maintaining it.
Adopt it — I transfer the GitHub repo and Vercel project to the org, and the site becomes official; I stay on as a maintainer if useful.
In-repo docs — I re-port the content into this repo’s docs/ as PRs, structured however you’d like it split.
No pressure and no rush — if it’s useful later rather than now, it’ll still be here. Feedback on gaps or inaccuracies is equally welcome; the fact-checking pass found and fixed a number of drift points, and fresh eyes catch more.
Thanks for the reviews on the recent PRs — the fast merges made the current docs possible.
Hi wallbreaker maintainers and contributors,
I’ve built and maintain an unofficial documentation site for wallbreaker: https://wallbreaker-docs.vercel.app (source: https://github.com/ra-co88/wallbreaker-docs, Nextra/Next.js, deployed on Vercel).
The site covers what the in-repo docs don’t yet: a Getting Started path, Concept pages (agent loop, engagement model, sessions & findings), Guides (payloads, personas, campaigns, multimodal, scripting/CI, troubleshooting), full Reference (all 51 presets, 71 transforms, 100+ tools with parameters verified against the code, CLI reference, MCP server), and Policy pages (methodology, security, responsible use). Every command, config block, and parameter was fact-checked against the codebase rather than generated and trusted.
The site is live and I’ll keep maintaining it either way — but since it’s the team’s project, I wanted to put it on the team’s radar and offer options, in whatever direction you prefer:
Link it — a line in the README (“community docs”) is all it takes; I keep hosting and maintaining it.
Adopt it — I transfer the GitHub repo and Vercel project to the org, and the site becomes official; I stay on as a maintainer if useful.
In-repo docs — I re-port the content into this repo’s docs/ as PRs, structured however you’d like it split.
No pressure and no rush — if it’s useful later rather than now, it’ll still be here. Feedback on gaps or inaccuracies is equally welcome; the fact-checking pass found and fixed a number of drift points, and fresh eyes catch more.
Thanks for the reviews on the recent PRs — the fast merges made the current docs possible.