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/omerakben/code-oz/agents-mdgit clone --depth 1 https://github.com/omerakben/code-ozWhat 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.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
code-oz 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 yesterday.
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.
What it actually says
AGENTS.md — code-oz
This file is a pointer for Codex sessions. The canonical project orientation, non-negotiable rules, architecture locks, working conventions, and milestone cadence live in CLAUDE.md.
Read CLAUDE.md first. Then docs/design/ROADMAP.md for the milestone plan.
The two files are kept in sync by treating CLAUDE.md as the single source of truth: changes land there, and this file remains a one-line pointer to avoid drift.
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.
- yesterday First seen · 8 lines · 112 tokens per session scan A 4549bcdf9b6f
code-oz AGENTS.md is an instructions file published in the GitHub repository omerakben/code-oz (2 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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
code-assistant AGENTS.md
Instructions for stippi/code-assistant, covering repository guidance, essential commands, building and development, testing specific components and architecture overview.
nori-skillsets AGENTS.md
Instructions for tilework-tech/nori-skillsets, covering plugin package changes, claude code configuration vs. nori plugin package, skills documentation, style guide and functions and named parameters.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
open-plan-annotator AGENTS.md
Instructions for ndom91/open-plan-annotator, covering open-plan-annotator: development guide, what this is, architecture, runtime distribution and key files.
copperhead AGENTS.md
Instructions for copperheadhq/copperhead, covering agents.md, repository overview, sources of truth, build and verification and architecture.
copperhead CLAUDE.md
Instructions for copperheadhq/copperhead, covering claude.md, what this repo is, sources of truth, workflow (openspec) and architecture (per spec.md §2).