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/nexus-substrate/nexus-agents/agents-mdgit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/agents-md)<a href="https://agentmods.dev/instructions/nexus-substrate/nexus-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/nexus-substrate/nexus-agents/agents-md.svg" alt="Measured on agentmods" 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 | $0.11971 | $0.11971 |
| Opus 5 | $0.05986 | $0.05986 |
| Sonnet 5 | $0.02394 | $0.02394 |
| Haiku 4.5 | $0.01197 | $0.01197 |
Grade A, and why
nexus-agents 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 today.
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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — nexus-agents
Standalone guidance for AI coding agents (OpenCode, Codex CLI, Cursor, Aider, Cline, Continue, Goose, Claude Code) working in this repo. Self-contained — no required redirect to other files.
About this project: Nexus-agents is a governance substrate for AI coding agents — adversarial PR review, drift-detected charter, tamper-evident append-only audit chain (threat model: tamper-evident, not tamper-proof), closed-loop telemetry. The agents you (the reader) belong to are exactly the kind of agent nexus-agents governs. Rules in .rules/ are enforced by CI gates and PR-review voters, not just suggestions.
Canonical surface. This file is the single source of truth for agent guidance in this repo (per #2805's option-B federation). Every other harness config (
.cursor/rules/,.windsurf/rules/,.aider.conf.yml,.continue/rules/,.clinerules/) is a one-line redirect to this file — never duplicated content. PRs that duplicate content here into a harness-specific file get refactored to redirects before merge. See docs/architecture/AGENT_COMPATIBILITY.md for the full federation rationale.Claude Code users: the legacy entry point at CLAUDE.md is still authoritative for Claude-Code-specific integrations (auto-loaded rules, plugin marketplace). The content below is the harness-neutral subset.
Mission
Nexus-agents is a self-improving autonomous engine for an organization's technical work, built to extend toward its broader functions over time. It runs the engineering lifecycle end to end — form/refine intent → research → plan (agile PM: epics → child issues) → develop (multi-CLI) → adversarial-consensus review → QA + security gates → measure outcomes → self-tune. The routing/strategy self-improvement loop is wired and default-on (outcome telemetry → strategy distillation → bounded routing adjustment, enforce-by-default since v2.96). Coding was the deliberate bootstrap: build an engine good enough to extend itself to the remaining functions and keep improving how it works.
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.
- today Changed ff07d527bfbc
- 3d ago Changed · +11 lines · +299 tokens per session 2f6450629ee8
- 4d ago First seen · 490 lines · 11,672 tokens per session scan A b8387fd6bee6
nexus-agents AGENTS.md is an instructions file published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 11,971 tokens to every session, about $0.0599 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.