Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/safe-agentic-world/nomos/agents-mdgit clone --depth 1 https://github.com/safe-agentic-world/nomosWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00506 | $0.00506 |
| Opus 5 | $0.00253 | $0.00253 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
nomos AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Nomos is a Go codebase for a policy-enforced execution control plane. The CLI entrypoint lives in cmd/nomos. Core implementation packages live under internal/ and include areas such as policy, service, gateway, mcp, doctor, and executor. Example configs and quickstarts live in examples/. Starter policy bundles are in policies/, deployment artifacts in deploy/, docs in docs/, and reusable fixtures in testdata/.
Build, Test, and Development Commands
Use standard Go tooling from the repository root:
go build ./cmd/nomosbuilds the CLI.go test ./...runs the full test suite.go vet ./...runs static checks.go test ./internal/mcpruns focused MCP compatibility tests.go run ./cmd/nomos doctor -c ./examples/quickstart/config.quickstart.json --format jsonperforms a deterministic readiness check.
For quick local validation, keep the example configs and policy bundles working as checked in.
Coding Style & Naming Conventions
Format Go code with gofmt and follow standard Go naming. Keep behavior deterministic and fail closed. Reject unknown fields unless an API explicitly supports extensions. Use stable, descriptive rule IDs in policy bundles. Keep Markdown headings short and in Title Case. Prefer relative paths in checked-in sample configs.
Testing Guidelines
Add or update targeted unit tests in the package you change. Run focused tests first, then go test ./... before opening a PR. Preserve smoke coverage for CLI, policy, doctor, and MCP flows. When changing examples or workflows, verify the quickstart commands still work and keep .github/workflows/ci.yml green.
Commit & Pull Request Guidelines
Recent history uses short, imperative subjects, often with prefixes such as feat:, fix:, and chore:. Keep commits focused and descriptive, for example feat: add argv-aware exec policy matching. Pull requests should include a concise summary, linked issue or task, tests run, and any docs updates required by the change.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 28 lines · 506 tokens per session scan A 77e8395eb91d
nomos AGENTS.md is an instructions file published in the GitHub repository safe-agentic-world/nomos (18 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 506 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
jarvis-registry AGENTS.md
AGENTS.md instructions for ascending-llc/jarvis-registry, covering jarvis registry — agent guide, project overview, ⚠️ plan mode instructions ⚠️, my engineering preferences and 1. architecture review.
Unla CLAUDE.md
Claude Code instructions for AmoyLab/Unla, covering claude.md, project overview, development commands, go backend and run tests.
agent CLAUDE.md
Instructions for 1mcp-app/agent, covering claude.md, repository information, development commands, setup and build & run.
warden AGENTS.md
Instructions for stephnangue/warden, covering warden — agent guide, where to start, the agent loop, provider skills and adding a skill for a new provider.
mcpproxy-go AGENTS.md
Instructions for smart-mcp-proxy/mcpproxy-go, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
VaultysClaw CLAUDE.md
Instructions for vaultys/VaultysClaw, covering claude.md, commands, development, demo / simulator and build.