fak: Instructions file for Codex

AGENTS.md

fak AGENTS.md is an instructions file for Codex, OpenCode from anthony-chaudhary/fak. It costs 12,104 tokens per session, scanned A, original, Apache-2.0.

A repository instruction file that explains how coding agents should operate in the fak project.

In plain words
What is it for?
Guiding agents while they investigate, modify, test, and ship changes in fak.
Why use it?
It sets project-specific rules for scope, delegation, testing, and repository work.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

This is anthony-chaudhary/fak's own configuration. It tells Codex and OpenCode how to work on fak 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 fak configures →

Reuse

Borrowing it

Nothing to install: this file belongs to anthony-chaudhary/fak. 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/anthony-chaudhary/fak/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/anthony-chaudhary/fak

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 fak AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/anthony-chaudhary/fak/agents-md"><img src="https://agentmods.dev/badge/instructions/anthony-chaudhary/fak/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12,104 This file is loaded in full into every session.
When invoked 12,104 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.12104 $0.12104
Opus 5.5 $0.04842 $0.04842
Sonnet 5.5 $0.02421 $0.02421
Haiku 4.5 $0.01210 $0.01210

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

Security

Grade A, and why

fak 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 · 524 lines

How it starts

The opening of the file, as written. The whole thing — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — orientation for coding agents

Not the human contributor guide. This file is operating instructions for automated contributors working inside the maintainers' shared checkout — trunk guards, lane leases, commit trailers, and shared-tree rules that have no meaning outside it. If you are a human evaluating or contributing to fak, read README.md for what fak is and CONTRIBUTING.md for how to contribute; nothing below is required of you.

You are an autonomous agent working in this repo. This file is the machine-read entry point (the agents.md convention). It is intentionally command-dense and free of philosophy. For the why, read README.md; for a curated doc map, read llms.txt. Humans: see START-HERE.md.

Default scope when launched from this repo

When an agent is launched with this fak repository as its working directory, default all broad or underspecified work requests to FAK work in this repository. Requests such as “finish local WIP,” “work the backlog,” or “run agents all night” mean inspect, prioritize, implement, test, and ship FAK work; they do not authorize a workspace-wide sweep of sibling repositories.

Use FAK's guarded headless-agent and worker mechanisms for parallel or unattended work, following the lane, lease, worktree, landing, and witness rules below. Only inspect or modify another repository when the operator explicitly names that repository or the FAK task itself has a concrete, evidenced cross-repo dependency. When tasks involve shared interfaces (pkg/*), cross-repo platform integration, or dual-repo goal/lease coordination, synchronization MUST encompass both fak and fak-private companion repositories to prevent interface skew (go.work) and lease/queue stalls (refs/fak/locks/*). If scope is ambiguous, stay in FAK. Under the Companion-Aware Dev Harness, local development in fak is first-class and automatically governed by companion tooling: when fak-private is present side-by-side (via ../fak-private, go.work, or FAK_PRIVATE_ROOT), fak pre-commit hooks run 5-gate boundary checks (cmd/fak-boundary) and secret leak audits (tools/scrub_public_copy.py) by default, while fak-dev gate, fak-dev provenance, fak-dev audit-leak, and fak-dev ticket bridge directly to companion tools without requiring directory switches. Full architecture specification: docs/architecture/companion-dev-harness.md.

Read the full file on GitHub · 524 lines

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 · -1 lines · -31 tokens per session fee7b9eabab9
  2. 16d ago Changed · +2 lines · +43 tokens per session 7341672d61a5
  3. 18d ago Changed · -291 tokens per session efd2f03886a3
  4. 23d ago Changed · +1 lines · +348 tokens per session cf161700d940
  5. 25d ago Changed · +14 lines · +324 tokens per session 2bd043c7d8f4
  6. 1mo ago Changed · +47 lines · +1,165 tokens per session c2e30ce15926
  7. 1mo ago Changed · +43 lines · +1,197 tokens per session 68e270d4544e
  8. 1mo ago Changed · +7 lines · +433 tokens per session 9c73d5d4b9e0
  9. 1mo ago Changed · +33 lines · +1,045 tokens per session e2a51d9ee261
  10. 1mo ago First seen · 378 lines · 7,871 tokens per session scan A d15fd5dfcf61

Subscribe to this mod's changes

fak AGENTS.md is an instructions file published in the GitHub repository anthony-chaudhary/fak (42 stars, last pushed today), licensed Apache-2.0. It adds 12,104 tokens to every session, about $0.0484 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-03.

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,649 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,549 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