What is codex-office-playbook AGENTS.md?

Project instructions for an office-operations framework built around rules, roles, skills, scripts, templates, and workflows. They describe how to understand business work, automate repeatable tasks, and handle integrations safely.

Use them when adding or changing office workflows, agents, skills, scripts, documents, or external integrations. They also cover required briefs, specifications, ownership, and success criteria.

They give contributors a consistent way to turn unclear requests into specifications and to avoid unsafe changes, exposed secrets, and undocumented automation.

How sergeionlyart/codex-office-playbook configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to sergeionlyart/codex-office-playbook. 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/sergeionlyart/codex-office-playbook/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/sergeionlyart/codex-office-playbook

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/sergeionlyart/codex-office-playbook/agents-md/github.svg)](https://agentmods.dev/instructions/sergeionlyart/codex-office-playbook/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/sergeionlyart/codex-office-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/sergeionlyart/codex-office-playbook/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/sergeionlyart/codex-office-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/sergeionlyart/codex-office-playbook/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 522 This file is loaded in full into every session.

When invoked 522 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.

Model	Per session	Once invoked
Fable 5.1	$0.00522	$0.00522
Opus 5	$0.00261	$0.00261
Sonnet 5	$0.00104	$0.00104
Haiku 4.5	$0.00052	$0.00052

Measured 9d ago against content hash 7e50024dc271, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

codex-office-playbook 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 9d 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 · 57 lines

What it actually says

AGENTS.md

Роль этого проекта

Этот репозиторий — каркас для офисной операционной работы с Codex.
Рассматривай его не как демонстрацию функций, а как рабочую систему, где есть:

правила;
роли;
skills;
scripts;
шаблоны документов;
карта процессов;
политика безопасной публикации.

Как работать в этом проекте

Сначала пойми бизнес-задачу, потом переходи к реализации.
Если запрос сырой, сначала превращай его в структурированный brief.
Для повторяемых операций предпочитай deterministic scripts.
Для гибких интеллектуальных процедур предпочитай skills и шаблоны.
Перед добавлением нового сценария проверь, нельзя ли расширить существующий skill или script.
После добавления нового skill, script, role или workflow обновляй реестры в docs/.
Не храни секреты, токены, приватные ключи и реальные клиентские данные в репозитории.
Не выполняй внешние destructive-действия без явной необходимости и проверки.
Любая интеграция с внешней системой должна сначала получить краткую спецификацию: входы, выходы, маппинг полей, ограничения, dry-run, rollback.
Любая новая automation-задача должна получить:

brief;
spec;
понятное имя;
владельца;
критерий завершения.

Что читать в первую очередь

README.md
docs/START-HERE.md
docs/WORKFLOW-MAP.md
docs/OFFICE-POLICY.md
.codex/README.md

Правила модификации проекта

Делай минимально достаточные изменения.
Не переименовывай существующие файлы без причины.
Не ломай совместимость шаблонов и реестров.
Если видишь дублирование, сначала предложи упрощение структуры, потом меняй её.
Если создаёшь новый script, добавь короткую документацию и тестовый каркас.
Если создаёшь новый skill, дай ему узкую, ясную зону ответственности.

Стандарт выходного результата

Когда задача завершена, в ответе или handoff должно быть ясно:

что именно изменено;
где это лежит;
что запускать дальше;
какие есть ограничения, допущения и риски.

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.

9d ago First seen · 57 lines · 522 tokens per session scan A 7e50024dc271

Subscribe to this mod's changes

codex-office-playbook AGENTS.md is an instructions file published in the GitHub repository sergeionlyart/codex-office-playbook (2 stars, last pushed 4mo ago), licensed MIT. It adds 522 tokens to every session, about $0.0026 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.

Productivity

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,296 tokens

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.

openai/codex · 5,153 tokens

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 · 6,785 tokens

codex-office-playbook: Instructions file for Codex