agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/libraries/go/worker/AGENTS.md

nvcf / worker

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

Native Go library for worker-side NVCF helpers: API clients, NATS consumers, proxy utilities, tracing, metering, auth, and test fixtures. CI subproject id: go-worker. The umbrella uses the go-tool profile in tools/ci/subproject-validations.yaml, an internal GitLab CI config not present in this public snapshot.

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

    Do not hand-edit generated protobuf files under proto/.

    line 28
  2. Distinctive:

    Keep test utilities fake-only.

    line 29

≈ “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 - go worker library

Native Go library for worker-side NVCF helpers: API clients, NATS consumers, proxy utilities, tracing, metering, auth, and test fixtures.

Layout

  • nvcf/ and nvct/: service clients and worker connection helpers
  • consumer/: NATS work request consumer
  • proxy/: HTTP/3, reverse proxy, routing, and connection helpers
  • proto/: generated NVCF and NVCT protobufs
  • tracing/, metrics/, metering/: observability helpers
  • test/testutils/: mock NVCF, NVCT, NATS, OTEL, and artifact servers

Build and Test

go test ./...
go build ./...

CI subproject id: go-worker. The umbrella uses the go-tool profile in tools/ci/subproject-validations.yaml, an internal GitLab CI config not present in this public snapshot.

Local Gotchas

  • Do not hand-edit generated protobuf files under proto/.
  • Keep test utilities fake-only; do not commit real service tokens or endpoints.
  • This module depends on shared Go library patterns from src/libraries/go/lib.

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