agentleFS
Sign inStart free
famclawfamclaw/honeybadger/CLAUDE.md

honeybadger

CLAUDE.md4 starsChanged 4 months agoMITView on GitHub

What this is Go security scanner for AI agent skills and MCP servers. Scans for hardcoded secrets, CVEs, supply-chain risk, and build provenance before install. CLI + MCP server modes. MIT licensed. Code structure - Scanners in internal/scanner/: secrets, supplychain, cve, meta, capability, skillsafety, mcptool, attestation - Core types in internal/scan/: Finding, Options, helpers - Engine in internal/engine/: scanner list, verdict logic - Entry points: cmd/honeybadger/main.go (CLI), cmd/honeybadger/mcp.go (MCP) Coding rules - Go language only - Every scanner change requires…

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every scanner change requires matching test fixture

    line 14
  2. Very specific:

    Run make self-check before submitting (HoneyBadger scans itself)

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

HoneyBadger Agent Instructions

What this is
Go security scanner for AI agent skills and MCP servers. Scans for hardcoded secrets, CVEs, supply-chain risk, and build provenance before install. CLI + MCP server modes. MIT licensed.

Code structure

  • Scanners in internal/scanner/: secrets, supplychain, cve, meta, capability, skillsafety, mcptool, attestation
  • Core types in internal/scan/: Finding, Options, helpers
  • Engine in internal/engine/: scanner list, verdict logic
  • Entry points: cmd/honeybadger/main.go (CLI), cmd/honeybadger/mcp.go (MCP)

Coding rules

  • Go language only
  • Every scanner change requires matching test fixture
  • Fixtures must build secrets at runtime (not hardcoded) to avoid GitHub push protection
  • Run make self-check before submitting (HoneyBadger scans itself)

Build & test

  • make build
  • make test
  • make self-check
  • Integration tests: go test -tags integration ./...

Module path
github.com/famclaw/honeybadger

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free