agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/deploy/helm/llm-request-router/AGENTS.md

nvcf / llm-request-router

AGENTS.md261 starsChanged 9 days agoApache-2.0View on GitHub

Keep templates and values consistent with the existing chart helpers. Extend the render checks under scripts/ when changing generated resources. Run from this directory: Meaningful Stargate chart changes must satisfy the Stargate mock integration and performance gates. Deploy the candidate chart in the chosen runtime mock test. Render checks alone do not validate registration, transport, readiness, or request handling. Resource, scheduling, and router-policy changes require baseline/candidate performance evidence. Follow the root local QA safety rules before changing a test environment.…

The file

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

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

  • ≈2

    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. Very specific:

    Keep templates and values consistent with the existing chart helpers.

    line 3
  2. Distinctive:

    Run from this directory:

    line 8
  3. Common:

    Follow the root local QA safety rules before changing a test environment.

    line 25
  4. Common:

    Use plain ASCII in committed prose and keep secrets out of render output.

    line 26

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

LLM request router chart

Keep templates and values consistent with the existing chart helpers. Extend the render checks under scripts/ when changing generated resources.

Build and test

Run from this directory:

helm lint ./llm-request-router
make test
git diff --check

Pull Request gates

Meaningful Stargate chart changes must satisfy the Stargate mock integration and performance gates. Deploy the candidate chart in the chosen runtime mock test. Render checks alone do not validate registration, transport, readiness, or request handling. Resource, scheduling, and router-policy changes require baseline/candidate performance evidence.

Follow the root local QA safety rules before changing a test environment. Use plain ASCII in committed prose and keep secrets out of render output.

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