CodexPotter AGENTS.md

Repository guidelines for an AI coding agent that prioritize simple, readable, maintainable code. They also explain how to preserve changes already made by the user.

In plain words
What is it for?
Planning and reviewing code changes, deciding when abstractions are justified, keeping functions focused, reducing unnecessary public interfaces, and protecting existing work.
Why use it?
They help keep new code understandable and avoid accidentally discarding work that belongs to someone else.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/breezewish/codexpotter/agents-md
Clone the repo
git clone --depth 1 https://github.com/breezewish/CodexPotter

Made for: Codex, OpenCode.

Per session 306 This file is loaded in full into every session.
When invoked 306 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00306 $0.00306
Opus 5 $0.00153 $0.00153
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00031 $0.00031

Measured 3d ago against content hash 24716380d908, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

CodexPotter 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 3d 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

Repository Guidelines

Workflow Principles

  • NEVER use git to discard or revert any changes not made by you - they are proposely changed by user and you should live with that.

Engineering Rules

This project requires extremely high code quality and maintainability. Best engineering practices must be followed at all times.

The rules below are some typical principles. They are not exhaustive, and you must always use your best judgment to write the cleanest code possible. You must always clean up and refactor immediately when you see opportunities or any violations of these engineering rules.

Core Principles: Simplicity & Readability

  • Boring Code - Obvious, self-explanatory > clever, minimize cognitive load
  • Single Responsibility - One function, one job
  • Explicit over Implicit - Clear is better than concise
  • Meaningful Abstractions - Only when they reduce cognitive load
  • Keep DRY - Only if it does not conflict with the above principles

Better Maintainability

  • Keep the public API surface minimal; prefer reusing existing methods
  • Don't treat "looks similar" as "equivalent"
  • Abstractions must be meaningful
  • Keep certainty, single source of truth - e.g. don't introduce "optional" unless absolutely necessary
  • Always add clear, concise and explicit doc comments for public APIs, complex logic, and non-obvious code

Naming Symbols

  • Choosing the name that needs the least explanation, consider: verb clarity, noun specificity, context
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. 3d ago First seen · 32 lines · 306 tokens per session scan A 24716380d908

Subscribe to this mod's changes

CodexPotter AGENTS.md is an instructions file published in the GitHub repository breezewish/CodexPotter (630 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 306 tokens to every session, about $0.0015 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.