pollux: Instructions file for Codex

AGENTS.md

pollux AGENTS.md is an instructions file for Codex, OpenCode from Wsyjq/pollux. It costs 274 tokens per session, scanned A, original, MIT.

A set of mandatory instructions for working on the Wsyjq/pollux project, including how to use its project memory and record engineering work.

In plain words
What is it for?
Use it when starting work in that project, changing files, recording bugs and fixes, or preserving decisions and notes.
Why use it?
It makes project-specific checks, change tracking, and documentation part of the normal development process.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is Wsyjq/pollux's own configuration. It tells Codex and OpenCode how to work on pollux 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 pollux configures →

View source ↗ Wsyjq/pollux
Reuse

Borrowing it

Nothing to install: this file belongs to Wsyjq/pollux. 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/Wsyjq/pollux/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Wsyjq/pollux

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 pollux AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/wsyjq/pollux/agents-md"><img src="https://agentmods.dev/badge/instructions/wsyjq/pollux/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 274 This file is loaded in full into every session.
When invoked 274 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.00274 $0.00274
Opus 5.5 $0.00110 $0.00110
Sonnet 5.5 $0.00055 $0.00055
Haiku 4.5 $0.00027 $0.00027

Measured 1mo ago against content hash baf0a0a49af3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 32 lines

What it actually says

AGENTS.md

Pollux Project Memory (MANDATORY)

This project uses projectmem as its persistent engineering memory.

At session start, call these MCP tools in order:

  1. get_instructions()
  2. get_summary()
  3. get_project_map() when structure matters
  4. get_plan() for current intent and parallel work

Before modifying a file, call precheck_file(path).

During work:

  • Log a bug with log_issue before attempting a fix.
  • Record every distinct attempt with record_attempt and its real outcome.
  • Call record_fix only after verification.
  • Record durable choices with add_decision and gotchas with add_note.
  • Include why the choice was made, rejected alternatives, and evidence.

Source-of-truth boundary:

  • Never hand-edit events.jsonl, summary.md, or generated issues/*.md.
  • Maintain PROJECT_MAP.md directly when structure or relationships change.
  • Maintain plan.md directly for ideas, active plans, and shipped work.
  • Before finishing, call get_summary() and confirm the session is recorded.

Git hooks are advisory. Search by commit title and inspect the event's git_commit field before claiming auto-capture worked.

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. 1mo ago First seen · 32 lines · 274 tokens per session scan A baf0a0a49af3

Subscribe to this mod's changes

pollux AGENTS.md is an instructions file published in the GitHub repository Wsyjq/pollux (1 stars, last pushed 2mo ago), licensed MIT. It adds 274 tokens to every session, about $0.0011 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

vscode design-tokens.instructions.md

Design-system size tokens (spacing, corner radius, font size, codicon size, stroke). Use when writing or editing CSS to size, space, or round UI — prefer the --vscode- token vars over hardcoded px values.

microsoft/vscode · 2,578 tokens