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/rockielab/rockie-codex/agents-mdgit clone --depth 1 https://github.com/Rockielab/rockie-codexWrote 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/rockielab/rockie-codex/agents-md)<a href="https://agentmods.dev/instructions/rockielab/rockie-codex/agents-md"><img src="https://agentmods.dev/badge/instructions/rockielab/rockie-codex/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.00905 | $0.00905 |
| Opus 5 | $0.00452 | $0.00452 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
rockie-codex 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How to work in rockie-codex
Local overlay for the official codex binary. Customizes the runtime in a per-tenant Fly machine when MODE=subscription and BINARY=codex.
For what this repo does for you as a researcher, see README.md. For cross-repo orientation (the four-harness model + alignment agent), see ../docs/architecture.md in the workspace meta-repo.
First reads (after the workspace docs/ reads)
README.md— researcher-facing overview.project-extension/— repo-installed extension layer.user-extension/— user-global extension layer.agents-md/— AGENTS.md templates that get rendered into tenant projects.
⚠️ This repo is a LOCAL OVERLAY, not the canonical source
Skills, hooks, memory schema, scripts → canonical source is ../platform-skills/.
The runtime image's assemble-skills.sh pulls from platform-skills/ (NOT from this repo) and writes to ~/.codex/skills/ inside the per-tenant machine. This repo is a local copy used for development reference.
The Phase 6 alignment agent propagates changes from platform-skills/ into this repo's mirror copies. Don't edit skills here directly — edit them in platform-skills/ and let the alignment agent push.
The exceptions are intentional divergences (in .claude/skills/align-overlays/intentional-divergences.yaml in the meta-repo): codex-side conventions like agents-md/ templates, natural-language invocation style (vs claude's claude-md/ and slash commands), and hooks.json (vs claude's hooks/ directory).
Process for changes here
- Is this a skill/hook/memory change? Edit
platform-skills/instead. Don't fork here. - Is this an agents-md template change? Edit
agents-md/here. The alignment agent will mirror torockie-claude/claude-md/with translation (AGENTS.md ↔ CLAUDE.md, NL invocation ↔ slash commands). - Is this a structural change to project-extension/ or user-extension/? Likely affects rockie-claude too — flag in the PR description.
- Tests:
pnpm test(codex-extension's vitest config, lint via tests.yml). - Commit: Sam Larson author, no AI trailers, Conventional Commits.
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.
- 4d ago First seen · 50 lines · 905 tokens per session scan A 95534901e905
rockie-codex AGENTS.md is an instructions file published in the GitHub repository Rockielab/rockie-codex (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 905 tokens to every session, about $0.0045 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.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.