honeybadger-dev
Skill4 starsChanged 4 months agoMITView on GitHub
How to add a scanner, lockfile parser, or rule to HoneyBadger, plus the test-fixture and self-check requirements. Use when extending scanners or contributing to honeybadger.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- honeybadgerSkill
The file
Files
HoneyBadger — extending scanners
Adding a scanner
- New scanner = its own package under
internal/scanner/<name>/. - Register it in
internal/engine/engine.go(scanner list + verdict weighting). - Ship a matching fixture in
internal/testfixture/— fixtures build secrets at runtime (never hardcoded) so GitHub push protection doesn't reject the push.
Common extensions
- New lockfile parser (Cargo.lock, pnpm-lock.yaml, poetry.lock): add in
internal/scanner/cve/deps.go. - New supply-chain rule / secret pattern: add YAML under
rules/(embedded viarules/embed.go). - Typosquat dictionary entries:
internal/scanner/supplychain. - New test fixture: add to
internal/testfixture/with secrets built at runtime.
Before submitting
make build · make test · make self-check (scans itself) · go test -tags integration ./.... Open the PR against main.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

