agentleFS
Sign inStart free
MongoDBKnown publishermongodb/kingfisher/crates/kingfisher-rules/AGENTS.md

kingfisher / kingfisher-rules

AGENTS.md1.3k starsChanged 10 days agoApache-2.0View on GitHub

Follow the repository AGENTS.md. Existing Kingfisher YAML and Betterleaks TOML rules must continue to load and work without edits. New fields need backward-compatible defaults and must not silently change legacy validation/revocation behavior. Test unmodified legacy inputs. HTTP fallback profiles are optional, limited to two, and require runtime opt-in. Their reuse_primary_validation_logic and reuse_primary_revocation_logic booleans default to false. Validation reuse replaces only the primary HTTP URL; otherwise a complete HTTP validation is required. Revocation reuse requires explicit replacement URL(s), preserving the original…

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about mongodb/kingfisher

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Hacker News (51 times).

On GitHub · 50

45 more on GitHub

The file

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

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow the repository AGENTS.md.

    line 3
  2. Very specific:

    Never implicitly inherit revocation or try alternative mutation targets.

    line 12
  3. Distinctive:

    Keep legacy scalar/list HTTP URL inputs readable.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
AGENTS.md

Rules compatibility

Follow the repository AGENTS.md. Existing Kingfisher YAML and Betterleaks TOML rules must continue to load and work without edits. New fields need backward-compatible defaults and must not silently change legacy validation/revocation behavior. Test unmodified legacy inputs.

HTTP fallback profiles are optional, limited to two, and require runtime opt-in. Their reuse_primary_validation_logic and reuse_primary_revocation_logic booleans default to false. Validation reuse replaces only the primary HTTP URL; otherwise a complete HTTP validation is required. Revocation reuse requires explicit replacement URL(s), preserving the original HTTP action or multi-step program. Otherwise use an independent action or leave revocation unavailable. Never implicitly inherit revocation or try alternative mutation targets. The CLI opt-in is --fallbacks. Describe reuse as sharing logic while explicitly replacing the target URL(s), never copying the primary destination. Keep legacy scalar/list HTTP URL inputs readable; do not migrate the bundled detection catalog just to enable optional fallback behavior.

Built-in catalog

  • Exclude all filename-only/path-only detectors from built-in imports, including upstream rules with a path but no content regex. Do not add them to the bundle or rely on runtime exclusions.
  • Preserve content detectors that also restrict matching by path. Keep filename-only support available for explicit custom Kingfisher YAML and Betterleaks TOML rules, including their native callback-budget safeguards.
  • Generally useful detectors and validation improvements must go upstream to Betterleaks. Direct first-party rules in data/kingfisher-rules.yml are rare exceptions requiring a specific reason that requires shipping in Kingfisher itself, source/license provenance, tests, and a retirement condition in data/kingfisher-rules.md. Convenience or an unsubmitted upstream change is not sufficient. Replace temporary exceptions when a compatible upstream detector becomes available.
  • First-party exceptions feed the same maintainer-generated bundle, readable catalogs, provenance, notices, and verification pipeline as imported detectors. Do not add another catalog or runtime loader. Preserve the three broad Betterleaks generic-rule exclusions.

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