Borrowing it
Nothing to install: this file belongs to chi-qhsun/Codex-Semantic-Review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chi-qhsun/Codex-Semantic-Review/master/AGENTS.mdgit clone --depth 1 https://github.com/chi-qhsun/Codex-Semantic-ReviewWrote 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/chi-qhsun/codex-semantic-review/agents-md)<a href="https://agentmods.dev/instructions/chi-qhsun/codex-semantic-review/agents-md"><img src="https://agentmods.dev/badge/instructions/chi-qhsun/codex-semantic-review/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.1 | $0.00347 | $0.00347 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
Codex-Semantic-Review 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 5d 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.
What it actually says
Post-commit review reminder
After Codex successfully commits code, tests, build scripts, dependencies, or
runtime configuration, it must surface the $commit-review reminder before
handoff. The reminder is mandatory; invoking the MCP is explicit and optional.
Pure documentation, image, license, and other non-runtime commits are excluded.
When review is requested:
- Resolve the exact repository and pending committed SHAs. Never include uncommitted working-tree changes in the committed diff.
- Prefer
prepare_commit_history_reviewfor multiple SHAs, then author every required file, function, block, and line explanation. Use stable plan item IDs; if no build plan exists, retain the MCP'sauto-generated / unplannedplan instead of inventing a user-authored plan. - Call
create_commit_history_reviewwith the completed per-commit payloads andopen_browser=true. For one SHA, the compatible single-commit tools are also valid. - Treat the MCP's semantic gate as authoritative once invoked. Preserve the localhost URL, root digest, per-commit receipts, important files, plan coverage, and file/function/block/line comment counts.
Project-specific instructions may add review context but must not silently suppress the reminder. Duplicate global, project, skill, or hook reminders are deduplicated by repository, session, and SHA. Amend or rebase replacements are reviewed under their new SHA; unreachable superseded SHAs are not active.
This workflow never authorizes push, merge, upload, or unrelated process
changes. The site remains local to 127.0.0.1.
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.
- 5d ago First seen · 30 lines · 347 tokens per session scan A aa49d5326394
Codex-Semantic-Review AGENTS.md is an instructions file published in the GitHub repository chi-qhsun/Codex-Semantic-Review (0 stars, last pushed 12d ago), licensed MIT. It adds 347 tokens to every session, about $0.0017 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.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.