Polaris: Instructions file for Codex

AGENTS.md

Polaris AGENTS.md is an instructions file for Codex, OpenCode from sponge-b0b/Polaris. It costs 4,419 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for Polaris that define how coding agents should work, which project sources are authoritative, and which domain terms and secrets-handling rules to follow. AGENTS.md is a file used to give coding agents project-specific guidance.

In plain words
What is it for?
Use them at the start of Polaris tasks, especially when checking architecture, interpreting domain vocabulary, reviewing documentation, or deciding which source should control a change.
Why use it?
They help agents resolve conflicts between code, configuration, decisions, and documentation instead of silently choosing one source. They also prevent unnecessary loading of project context.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md; $skill-name invocation.

This is sponge-b0b/Polaris's own configuration. It tells Codex and OpenCode how to work on Polaris itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Polaris configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/sponge-b0b/Polaris

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Polaris AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sponge-b0b/polaris/agents-md/github.svg)](https://agentmods.dev/instructions/sponge-b0b/polaris/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/sponge-b0b/polaris/agents-md"><img src="https://agentmods.dev/badge/instructions/sponge-b0b/polaris/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.

agentmods 80×15 button for Polaris AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,419 This file is loaded in full into every session.
When invoked 4,419 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04419 $0.04419
Opus 5.5 $0.01768 $0.01768
Sonnet 5.5 $0.00884 $0.00884
Haiku 4.5 $0.00442 $0.00442

Measured 7d ago against content hash 74653d4f6719, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 7d 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.

AGENTS.md · 543 lines

How it starts

The opening of the file, as written. The whole thing — 543 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:

  1. Match claims to the correct authority:
    • code, configuration, executable checks, and relevant tests outside legacy/ → current implementation reality;
    • accepted CCL contracts → canonical material delivery semantics where a CCL contract exists;
    • accepted ADRs outside legacy/ → active architectural rationale/decisions not superseded by a canonical CCL field;
    • 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.
  2. If applicable authorities materially disagree, surface [source-conflict]. Do not silently choose whichever source makes the task easiest.
  3. Merge these repository rules with narrower user instructions for the active task.

Where a material semantic coordinate is represented by CCL, downstream prose may explain or project it but may not override it.

Proactive Attention Duty

At any time during analysis, planning, architecture, design, specification, ticketing, implementation, verification, review, remediation, or ordinary repository work, surface material concerns promptly when you notice them.

The current task is the immediate work surface, not the boundary of Attention. Maintain a Polaris-wide meta-level Attention posture across materially implicated product intent, domain semantics, architecture, authority, code, persistence, APIs, tests, docs/wiki, workflow state, and upstream/downstream contracts.

Use this materiality threshold:

Would a competent architect who understood Polaris as a whole want this brought to their attention now?

Read the full file on GitHub · 543 lines

Changes

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.

  1. 7d ago Changed · +6 lines · +44 tokens per session 74653d4f6719
  2. 8d ago Changed · -88 lines · -4,068 tokens per session 47e1ef54cc42
  3. 22d ago Changed · +24 lines · +536 tokens per session 2e778ee016dd
  4. 28d ago Changed · +48 lines · +918 tokens per session a7c989e5c4f5
  5. 1mo ago Changed · +4 lines · +115 tokens per session 1249a5260378
  6. 1mo ago Changed · +74 lines · +1,131 tokens per session c4de2dae0097
  7. 1mo ago Changed · +51 lines · +587 tokens per session 13a27ac29edb
  8. 1mo ago Changed · +31 lines · +617 tokens per session 2925f1c7c860
  9. 1mo ago Changed · +52 lines · +1,095 tokens per session aae6fdf3dd29
  10. 1mo ago First seen · 341 lines · 3,444 tokens per session scan A c27bdc07fca0

Subscribe to this mod's changes

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 4,419 tokens to every session, about $0.0177 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens