Borrowing it
Nothing to install: this file belongs to SunrisesIllNeverSee/agent-universe. 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/SunrisesIllNeverSee/agent-universe/main/AGENTS.mdgit clone --depth 1 https://github.com/SunrisesIllNeverSee/agent-universeWrote 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/sunrisesillneversee/agent-universe/agents-md)<a href="https://agentmods.dev/instructions/sunrisesillneversee/agent-universe/agents-md"><img src="https://agentmods.dev/badge/instructions/sunrisesillneversee/agent-universe/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/sunrisesillneversee/agent-universe/agents-md"><img src="https://agentmods.dev/badge/instructions/sunrisesillneversee/agent-universe/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.05042 | $0.05042 |
| Opus 5.5 | $0.02017 | $0.02017 |
| Sonnet 5.5 | $0.01008 | $0.01008 |
| Haiku 4.5 | $0.00504 | $0.00504 |
Grade A, and why
agent-universe 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 14d 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 — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SESSION COORDINATION — read FIRST (every session, every time)
This repo runs multiple parallel AI terminal sessions. To stop coordination from disappearing between sessions:
-
The bus is
Devins_Plans/SCRATCHPAD.md. Read its tail + the COORDINATION PROTOCOL header before doing anything. Append your status/decisions/questions there (format:### ⤷ <FROM> → <TO>: <subject>). Don't start a parallel log. -
Log into the activity tracker (once per session):
bash scripts/set-role.sh LEAD(orDEVIN/CODEX/COPILOT/GTM/ whatever you name your sessions). This writes a per-session role file that the PostToolUse hook reads to stamp your role into ACTIVITY.log. Without it, your edits log asUNKNOWN. Then update your row inDevins_Plans/state/ROSTER.md. -
Claim your lane before starting work. Append to
.agents/claims.yamlwith the file paths you intend to touch. Check for overlapping claims first. Release the claim when done (setreleased_at). -
Install the commit-log hook once per clone:
bash scripts/install-hooks.sh(git hooks live in.git/and don't travel with clone/push — each session/machine must install). -
Check cross-repo sync:
bash scripts/lanes.sh— shows every repo's version, branch, unpushed/behind/dirty status, and registry-published vs local versions. Read-only, changes nothing. -
See roster + activity side by side:
bash scripts/status.sh -
Validate coordination state:
python3 scripts/check.py— catches stale claims, overlapping lanes, migration number conflicts. -
OKF convention: every doc in
Devins_Plans/carries YAML frontmatter (type/title/description/tags/timestamp). New docs MUST include it. Lint withnode scripts/check-okf.mjs. -
DECISIONS.md: if you're wondering "why is X like this?", check
Devins_Plans/DECISIONS.mdfirst. If the answer isn't there, add it. -
Handoffs: use
Devins_Plans/handoffs/for structured cross-session transfers. Format:{date}-{from}-to-{to}-{topic}.md. Handoffs are immutable — never edit or rename another session's; new state = a new handoff. Role-scoped handoffs generated byscripts/handoff.shuseHANDOFF_<ROLE>_<YYYY-MM-DD>_<HHMM>.md. -
Stay in your lane. Claims (rule 3) define your write scope. Everything else — other sessions' handoffs, STATE fields, scratchpad entries, commits — is read-only context. A dangling commit or stale entry is a note on the bus, not a task to absorb. When asked for status or a handoff, report YOUR lane, not everyone's.
-
Cross-repo coordination:
Devins_Plans/CROSSWIRE.mdis the machine-local bus for handoffs that span repos. SCRATCHPAD is repo-local; CROSSWIRE is machine-local.
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.
- 14d ago Changed · +3 lines · +44 tokens per session ecef3d91e8e7
- 25d ago Changed · +9 lines · +133 tokens per session ba38f9b4f84f
- 28d ago Changed 3f35ba3e9e86
- 1mo ago Changed · +88 lines · +767 tokens per session 6cee575e7ac4
- 2mo ago First seen · 331 lines · 4,098 tokens per session scan A 3728cb42d25e
agent-universe AGENTS.md is an instructions file published in the GitHub repository SunrisesIllNeverSee/agent-universe (1 stars, last pushed 6d ago), licensed MIT. It adds 5,042 tokens to every session, about $0.0202 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-31.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.