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

kingfisher / kingfisher-python

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

Guidance for the native Python bindings in this subtree. - Follow the repository instructions and read the Python SDK architecture and compatibility guidance. Its principles apply to this bridge as well as the Python package. - Keep this crate focused on PyO3 conversions, native object ownership, execution controls, and exposing shared capabilities. Put reusable engine behavior in the appropriate shared crate and Python composition/ergonomics in python/. - Preserve public Python contracts when changing bindings, including exception mapping, result grouping, redaction,…

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, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Follow the repository instructions and read the Python SDK architecture and compatibility guidance.

    line 5
  2. Very specific:

    Keep this crate focused on PyO3 conversions, native object ownership, execution controls, and exposing shared capabilities.

    line 8
  3. Distinctive:

    Run affected Python tests and native/shared-crate checks.

    line 17

≈ “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

AGENTS.md

Guidance for the native Python bindings in this subtree.

  • Follow the repository instructions and read the Python SDK architecture and compatibility guidance. Its principles apply to this bridge as well as the Python package.
  • Keep this crate focused on PyO3 conversions, native object ownership, execution controls, and exposing shared capabilities. Put reusable engine behavior in the appropriate shared crate and Python composition/ergonomics in python/.
  • Preserve public Python contracts when changing bindings, including exception mapping, result grouping, redaction, deduplication, cancellation, and lifetime behavior. Rebuild the extension before testing Python-visible changes.
  • Preserve the configured Python compatibility and wheel targets. Keep GIL release, thread safety, shared runtime ownership, and optional shared-crate features explicit; do not introduce implicit CLI or Git subprocess dependencies.
  • Run affected Python tests and native/shared-crate checks. Update Python examples and documentation for exposed capabilities, even when implementation changes occur entirely in Rust.

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