Scouted · October 24, 2026
automated verified security vulnerability audits
Single-purpose Cloudflare security-audit skill, not a pack, but its value hinges on frontier-model access and Cloudflare's security credibility, so a solo dev can wrap it but can't easily match it.
Why now?
Coding agents are now capable enough to run multi-phase audits, and this repo's velocity (2,716 stars in a day, 21.25/day, 42.8k total, 2.6k forks) shows developers are actively reaching for agent-driven security tooling right now. The MIT license and small footprint (143 KB) make it immediately wrappable while the category is still forming.
The gap
The skill produces machine-readable, independently verified findings, but it ships as a skill, not a product: no hosted runner, no report delivery, no CI integration, no triage workflow. The gap is packaging verified agent audits into a repeatable pipeline for teams who won't wire up a skill themselves. Demand beyond GitHub is unproven — zero HN mentions, zero points/comments, no download or Reddit signals — so treat this as early interest, not validated willingness to pay.
Main competitor
The free MIT upstream Cloudflare skill itself, plus the coding agents users already run it inside.
Execution plan
- Fork the skill and build a thin CLI/wrapper that runs the multi-phase audit in CI and emits the machine-readable findings as SARIF/JSON for existing security dashboards.
- Ship a hosted 'audit-as-a-service' runner: point it at a repo, get a verified findings report with reproducible evidence per finding, since verification is the skill's core claim.
- Add a triage layer — dedupe, severity ranking, and false-positive feedback loop — so output is actionable rather than a raw agent transcript.
- Publish reproducible benchmark runs on public repos comparing findings against known CVEs to earn credibility a solo dev otherwise lacks versus Cloudflare's brand.
- Target the fork base (2,671 forks) directly with a migration path: drop-in config plus a free tier for open-source repos to convert GitHub intent into usage.
Monetization
Open-core: keep the wrapper MIT and charge a per-repo or per-seat subscription for the hosted runner, scheduled audits, and SARIF/CI integrations, with a free tier for public repos. No pricing claims beyond that — GitHub stars and forks show intent to use, not proven paid demand.