Manifest: Instructions file for Codex

AGENTS.md

Manifest AGENTS.md is an instructions file for Codex, OpenCode from iampawan/Manifest. It costs 1,634 tokens per session, scanned A, original, MIT.

A set of instructions for Manifest, a tool that takes a product requirements document from planning through building and launch. It defines checks for whether a requirements document is ready before development planning begins.

In plain words
What is it for?
Use it to score requirements, create tamper-evident hand-offs, verify gate results, and enforce Manifest's required planning checks.
Why use it?
It prevents teams from using hand-written approval results that cannot be verified, and makes the same checks work across different coding tools and continuous-integration systems.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/iampawan/manifest/agents-md"><img src="https://agentmods.dev/badge/instructions/iampawan/manifest/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,634 This file is loaded in full into every session.
When invoked 1,634 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.01634 $0.01634
Opus 5.5 $0.00654 $0.00654
Sonnet 5.5 $0.00327 $0.00327
Haiku 4.5 $0.00163 $0.00163

Measured 2mo ago against content hash 7f7c07e3dd56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Manifest 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 2mo 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 · 157 lines

How it starts

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

AGENTS.md — Manifest

Manifest takes a PRD from spec → build → launch with quality gates. Version 0.43.0.

Works in any agent. The gates are plain Node, so Codex, Cursor, Gemini CLI, Copilot, Aider, Windsurf, Zed and CI all get identical results. A gate code minted in one tool verifies in every other — it's a content hash, not a model judgement.

Ready Check needs nothing installed. scripts/ready-check.mjs is a single file with zero dependencies — Node 18+ and that one file is the whole PM-side gate. (Only the contract/repo tooling — validate.mjs, build-code-context.mjs — needs js-yaml: cd scripts && npm install.)


The one rule

Never hand-write a Ready Check hand-off, scorecard, or gate code. Always run the CLI and use its output verbatim. A hand-written block looks official and proves nothing — --verify reports UNVERIFIABLE because the • [id] … item list it hashes isn't there. Same for the score: run --scorecard, don't estimate it.


Ready Check — the PM gate (before dev grooming)

Score a PRD against the Definition of Ready, then mint a tamper-evident hand-off.

node scripts/ready-check.mjs --scorecard answers.json     # panel-like status
node scripts/ready-check.mjs --check     answers.json     # verdict JSON (exit 1 if not ready)
node scripts/ready-check.mjs --handoff   answers.json freeze.json   # hand-off + freeze stamp

answers.json:

{ "title": "<feature>",
  "items": {
    "goal":   { "detail": "..." },
    "design": { "na": true, "reason": "why it genuinely doesn't apply" },
    "metric": { "waived": true, "reason": "why it can't be answered yet" }
  } }

Workflow: read the PRD (fetch the link if you can) → map it to the items below → run --scorecard → show it → ask only for the gaps → fold the replies in → re-run until it clears → then --handoff.

The 11 required items

Read the full file on GitHub · 157 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. 2mo ago Changed 7f7c07e3dd56
  2. 2mo ago First seen · 157 lines · 1,634 tokens per session scan A 1705895f8256

Subscribe to this mod's changes

Manifest AGENTS.md is an instructions file published in the GitHub repository iampawan/Manifest (5 stars, last pushed 2mo ago), licensed MIT. It adds 1,634 tokens to every session, about $0.0065 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-08-31.

Related

Manifest AGENTS.md compared with instructions from other repositories

Manifest AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
Manifest AGENTS.mdiampawan/ManifestInstructions file52mo agoMITA1,634Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode