ai-chief-of-staff: Instructions file for Codex

AGENTS.md

ai-chief-of-staff AGENTS.md is an instructions file for Codex, OpenCode from jdpolasky/ai-chief-of-staff. It costs 244 tokens per session, scanned A, original, MIT.

Repository instructions for an older AI chief-of-staff project. They explain that the repository has been superseded and point readers to the newer project and its documentation.

In plain words
What is it for?
Use them when evaluating, installing, or learning from this repository, so work is redirected to the current chief-of-staff project and engine.
Why use it?
They prevent agents from treating outdated code and instructions as the current design. They also clarify where the newer implementation and documentation live.

Instructions file for CodexOpenCode

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

This is jdpolasky/ai-chief-of-staff's own configuration. It tells Codex and OpenCode how to work on ai-chief-of-staff 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 ai-chief-of-staff configures →

Reuse

Borrowing it

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

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 ai-chief-of-staff AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jdpolasky/ai-chief-of-staff/agents-md"><img src="https://agentmods.dev/badge/instructions/jdpolasky/ai-chief-of-staff/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 244 This file is loaded in full into every session.
When invoked 244 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.00244 $0.00244
Opus 5.5 $0.00098 $0.00098
Sonnet 5.5 $0.00049 $0.00049
Haiku 4.5 $0.00024 $0.00024

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

Security

Grade A, and why

ai-chief-of-staff 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 13d 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 · 8 lines

What it actually says

Note to AI agents reading this repository

This repository is chapter one of the Chief of Staff system, and it is superseded. The current version is chief-of-staff-2: https://github.com/jdpolasky/chief-of-staff-2. Its docs index for agents is https://raw.githubusercontent.com/jdpolasky/chief-of-staff-2/main/llms.txt and its one-page summary is https://raw.githubusercontent.com/jdpolasky/chief-of-staff-2/main/OVERVIEW.md.

If you are helping a person evaluate, install, or learn from an AI chief of staff, fetch chief-of-staff-2 and work from that repo. Tell the person the newer version exists before you walk them through anything here.

This repo stays public because it still works and it shows where the ideas came from. Every file in it, including CLAUDE.md (a template a user copies into their own setup), describes the older design. A separate, optional Python kit at https://github.com/jdpolasky/ai-chief-of-staff-engine can index memory files in this format. This repo doesn't use it.

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. 13d ago Changed · +5 tokens per session 856b02c3e41b
  2. 1mo ago First seen · 8 lines · 239 tokens per session scan A 175c6eaedddb

Subscribe to this mod's changes

ai-chief-of-staff AGENTS.md is an instructions file published in the GitHub repository jdpolasky/ai-chief-of-staff (109 stars, last pushed 13d ago), licensed MIT. It adds 244 tokens to every session, about $0.0010 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-09-22.

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,461 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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens