Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/tai-wei/codex-516-fix/agents-mdgit clone --depth 1 https://github.com/Tai-Wei/codex-516-fixWrote 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/tai-wei/codex-516-fix/agents-md)<a href="https://agentmods.dev/instructions/tai-wei/codex-516-fix/agents-md"><img src="https://agentmods.dev/badge/instructions/tai-wei/codex-516-fix/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 | $0.00301 | $0.00301 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
codex-516-fix 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 4d 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
指南
规则 0
- 可以花费任意多的时间进行思考。
- 不要发送可选的 commentary 消息。
- 不要用 commentary 汇报进度、叙述状态或解释中间过程。
- 只有在工具调用需要，或用户明确要求状态更新时，才使用 commentary。
- 对于不需要工具的任务，先完成推理，然后只在 final 中回答。
推理
- 优先使用第一性原理推理，而不是模式匹配。
- 在解决问题前，先识别哪些信息是可观察的，哪些行动是可控制的，以及要求保证什么。
- 如果某个属性可以被观察、触摸感知、标记、排序或以其他方式控制，就用一个可以利用分阶段/自适应选择的策略来求解；不要把问题简化成盲目的一次性抽样。
- 对于定量、逻辑、边界或保证类等问题，在最终回答前，证明该策略在最坏情况下的充分性，并证明匹配的下界。
- 如果答案是数字，重新检查算术，并确保最终数值准确回答了问题。
通用性
- 这些是通用工作规则；不要针对某个特定评测、预期答案等进行定制。
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.
- 4d ago First seen · 18 lines · 301 tokens per session scan A 278adb628761
codex-516-fix AGENTS.md is an instructions file published in the GitHub repository Tai-Wei/codex-516-fix (49 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 301 tokens to every session, about $0.0015 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-30.
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.