agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/invocation-plane-services/ratelimiter/AGENTS.md

nvcf / ratelimiter

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

Native Go image-source subtree for the NVCF rate limiter service. Bazel is the CI build path: Follow the release workflow for source versions and producer handoffs. - Do not hand-edit generated *.pb.go or *_grpc.pb.go files. - Change .proto files, then run go generate from both pb/ and nvcf/pb/ when those packages are affected. - protoc is required for proto regeneration. - Package tests under ratelimiter/cmd bind fixed local ports such as 127.0.0.1:3320; address conflicts are usually environmental. - New hand-authored…

The file

We split this AGENTS.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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Follow the release workflow for source versions and producer handoffs.

    line 25
  2. Very specific:

    Do not hand-edit generated *.pb.go or *_grpc.pb.go files.

    line 30

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

Native Go image-source subtree for the NVCF rate limiter service.

Layout

  • Go module: ratelimiter
  • Entrypoint: cmd/main.go
  • Protos: pb/ and nvcf/pb/

Build and Test

go build ./...
go test ./...
gofmt -w <changed-go-files>

Bazel is the CI build path:

bazel test //... --flaky_test_attempts=3

Follow the release workflow for source versions and producer handoffs.

Proto and Test Gotchas

  • Do not hand-edit generated *.pb.go or *_grpc.pb.go files.
  • Change .proto files, then run go generate from both pb/ and nvcf/pb/ when those packages are affected.
  • protoc is required for proto regeneration.
  • Package tests under ratelimiter/cmd bind fixed local ports such as 127.0.0.1:3320; address conflicts are usually environmental.
  • New hand-authored Go files must use the existing SPDX Apache-2.0 header. check-license enforces this at CI time.

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