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/sponge-b0b/polaris/agents-mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/agents-md)<a href="https://agentmods.dev/instructions/sponge-b0b/polaris/agents-md"><img src="https://agentmods.dev/badge/instructions/sponge-b0b/polaris/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.02256 | $0.02256 |
| Opus 5 | $0.01128 | $0.01128 |
| Sonnet 5 | $0.00451 | $0.00451 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
Polaris 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose and Authority
These are the operating rules for coding agents working on Polaris.
AGENTS.md is primarily prescriptive agent policy: how an agent must work in this repository. It is not a second authoritative copy of project architecture.
At the start of a task:
-
Match claims to the correct authority:
- code, configuration, executable checks, and relevant tests outside
legacy/→ current implementation reality; - accepted ADRs outside
legacy/→ active architectural decisions; - active architecture documents outside
legacy/→ current architectural description; - an active root
wiki/entities/, when present → derived architectural knowledge; legacy/v0_1/→ historical donor/reference material only, never current product, architecture, implementation, or workflow authority.
- code, configuration, executable checks, and relevant tests outside
-
If applicable authorities materially disagree, surface
[source-conflict]. Do not silently choose whichever source makes the task easiest. -
Merge these repository rules with narrower user instructions for the active task.
Domain Vocabulary
Do not preload CONTEXT.md.
Read CONTEXT.md only when:
- a domain term is ambiguous, contested, or new;
- canonical domain vocabulary is required for the current work;
- writing/updating an entity page where domain terminology is relevant;
- running
$domain-modeling.
Context compaction, conversation continuation, or task-state recovery does not by itself require re-reading CONTEXT.md.
If the required vocabulary is already established in the current task context, do not re-read CONTEXT.md unless it needs to be verified or refreshed.
CONTEXT.md is canonical domain vocabulary. Avoid duplicating it here.
Greenfield / Legacy Boundary
The canonical greenfield implementation lives under src/polaris/.
legacy/v0_1/ preserves the pre-greenfield Polaris platform as donor/reference material. New Polaris code, tests, configuration, migrations, tools, and runtime paths must not import, wrap, extend, execute through, or otherwise depend on legacy/.
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 · +13 lines · +383 tokens per session 2d75ea4b2324
- 5d ago First seen · 248 lines · 1,873 tokens per session scan A 94b45b438973
Polaris AGENTS.md is an instructions file published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 2,256 tokens to every session, about $0.0113 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-31.
Other instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).