Borrowing it
Nothing to install: this file belongs to safe-agentic-world/nomos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/safe-agentic-world/nomos/main/AGENTS.mdgit clone --depth 1 https://github.com/safe-agentic-world/nomosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/safe-agentic-world/nomos/agents-md)<a href="https://agentmods.dev/instructions/safe-agentic-world/nomos/agents-md"><img src="https://agentmods.dev/badge/instructions/safe-agentic-world/nomos/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/safe-agentic-world/nomos/agents-md"><img src="https://agentmods.dev/badge/instructions/safe-agentic-world/nomos/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00580 | $0.00580 |
| Opus 5.5 | $0.00232 | $0.00232 |
| Sonnet 5.5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
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 1mo 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 — 29 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, executor, and agenthook (the Claude Code and Codex hooks). Example configs, quickstarts, and incident regression suites live in examples/. Starter policy bundles are in examples/policies/, the default profiles in profiles/ (embedded copies are generated by make pin-profile-hashes), 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 test ./internal/agenthook -run Corpuschecks the real-world corpus golden; after an intended profile change, regenerate it with-update-corpusand review the diff.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.
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.
- 1mo ago Changed · +1 lines · +74 tokens per session 6928ce1a7201
- 1mo 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 (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 580 tokens to every session, about $0.0023 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.