agentleFS
The-Vibe-CompanyThe-Vibe-Company/quivr/sdks/AGENTS.md

quivr / sdks

AGENTS.md40k starsChanged 35 days agoMITView on GitHub

1 other project uses a version of this.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 5 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the The-Vibe-Company/quivr repository that our weekly crawl found: only 5 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

The file

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep SDK tests for distinct local risks: key-ring configuration and rotation, health exemptions, authentication before dispatch with no …

    line 4

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

SDK test ownership

  • Request-token verification belongs to the normative authentication cases, executed against both SDKs by the shared conformance script. Add cases there and prove each verifier guard with a mutation before removing SDK copies.
  • Keep SDK tests for distinct local risks: key-ring configuration and rotation, health exemptions, authentication before dispatch with no unauthenticated handler side effects, typed inputs, output validation, transport lifecycle and public fixture helpers.
  • Generator freshness belongs to the SDK check scripts. Model round trips and bundled-schema validation guard different contracts.
  • SDK manifest admission covers the shape and features that SDK dispatch needs. Engine-only semantic admission remains owned by the engine; consume normative fixtures for the SDK checks that apply.

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.