agentleFS
NVIDIAKnown publisherNVIDIA/nvcf/src/control-plane-services/nats-auth-callout/AGENTS.md

nvcf / nats-auth-callout

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

Native Go service that integrates with NATS Server authorization callouts. Authentication is plugin-based and currently covers NKey, OAuth2 JWT, and external webhook flows. For local iteration: Follow the release workflow for source versions and producer handoffs. When adding a plugin: Configuration precedence is CLI flags, then environment variables, then config file, then embedded defaults. Plugin routing uses account plus plugin name as the composite key.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the release workflow for source versions and producer handoffs.

    line 36
  2. Distinctive:

    When adding a plugin:

    line 41
  3. Very specific:

    Add the implementation under internal/plugins/<name>/.

    line 43
  4. Distinctive:

    Add focused tests and configuration docs.

    line 46
  5. Common:

    Keep NKey seeds, JWTs, webhook credentials, and API keys out of the repo.

    line 54
  6. Very specific:

    Use zaptest.NewLogger in tests that need logger isolation.

    line 55

≈ “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 - nats-auth-callout

Native Go service that integrates with NATS Server authorization callouts. Authentication is plugin-based and currently covers NKey, OAuth2 JWT, and external webhook flows.

Layout

  • cmd/nvcf-nats-auth-callout-service/: binary entrypoint and CLI commands
  • internal/service/: NATS callout integration and request coordination
  • internal/plugins/: auth plugins and plugin manager
  • internal/router/: Gin HTTP routing
  • internal/config/: Viper configuration
  • internal/tracing/: OpenTelemetry and Lightstep tracing
  • ../../../deploy/helm/nats-auth-callout/: Helm chart assets

Build and Test

make build
make test
make test-coverage
make coverage-check
make dev-lint

For local iteration:

make dev
make dev-debug
make dev-format
make dev-swagger

Follow the release workflow for source versions and producer handoffs.

Plugin Work

When adding a plugin:

  1. Add the implementation under internal/plugins/<name>/.
  2. Implement the plugin interface from internal/plugins/types.
  3. Register it in internal/plugins/manager.go.
  4. Add focused tests and configuration docs.

Configuration precedence is CLI flags, then environment variables, then config file, then embedded defaults. Plugin routing uses account plus plugin name as the composite key.

Local Gotchas

  • Keep NKey seeds, JWTs, webhook credentials, and API keys out of the repo.
  • Use zaptest.NewLogger in tests that need logger isolation.
  • make coverage-check enforces the local coverage threshold.
  • License headers are enforced by the goheader linter.

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.