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/powerfullz/override-rules/agents-mdgit clone --depth 1 https://github.com/powerfullz/override-rulesWrote 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/powerfullz/override-rules/agents-md)<a href="https://agentmods.dev/instructions/powerfullz/override-rules/agents-md"><img src="https://agentmods.dev/badge/instructions/powerfullz/override-rules/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.00907 | $0.00907 |
| Opus 5 | $0.00453 | $0.00453 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
override-rules 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
项目级 AI Agent 与贡献指南 (AGENTS.md)
欢迎！如果你是协助人类开发者参与本项目贡献的 AI Agent，或是想了解项目结构的贡献者，请务必阅读以下开发流与规范。
阅读docs/HOW_TO_CUSTOMISE.md以更好的帮助你所协助的人类自定义本项目的 Fork 或者贡献本项目。
🎯 核心架构与原则
- 源文件驱动：所有核心逻辑均采用 TypeScript 编写，存放在
src/与scripts/yaml_generator/目录中。src/main.ts：JS 动态覆写脚本的核心入口。scripts/yaml_generator/generator.ts：YAML 静态覆写文件的生成逻辑。
- 禁止直接修改产物：根目录下的
convert.js、convert.min.js以及yamls/目录的内容属于自动生成的构建产物（注意：它们已被main分支取消 Git 跟踪）。永远不要直接编辑这些产物文件。一切修改必须在.ts源码中进行。 - 构建工具链：我们使用
esbuild作为打包和压缩工具，可以通过编写的scripts/build.mjs脚本一次性地编译出包含了完整注释的产物文件。
🛠️ 开发与构建工作流
在修改源代码后，执行以下命令以验证更改并生成本地对应的产物文件：
npm run build: 运行scripts/build.mjs脚本，同时编译生成未压缩的convert.js与经过强力压缩的convert.min.js，并在顶部注入开源版权声明。npm run generate: 运行 YAML 覆写配置生成器，更新yamls/目录内的排列组合文件。npm run artifacts: 一键依次执行上述所有构建与生成阶段。
推荐在提交相关修改前，在终端运行 npm run artifacts 进行本地全量测试（确保没有编译报错、产生的体积符合正常逻辑）。
🧹 代码规范
- 统一格式化：本项目使用 ESLint 和 Prettier。修改完代码后，可以通过
npm run format及npm run lint:fix整理代码，遵循既有代码风格。 - 保持纯粹：对于
convert.min.js中的构建结果，项目脚本配置了--legal-comments=none去除多余注释，并自动添加统一的文件 Header Banner。
📦 提交与 PR 规范
- 分离提交：如果你的变动既包含核心功能的改动，又涉及相关文档的修改，尽量按有意义的逻辑分步提交。
- 文档同步：当新增了支持的 URL 参数（如在
src中）或是新增了 YAML 文件的组合选项时，务必同步修改README.md内对应的参数说明文档。
🚀 版本发布流程 (Release Workflow)
当需要发布新版本时，可以通过以下命令更新版本号并触发相关操作：
- 发布补丁版本 (Patch)：
npm version patch（适用于向后兼容的 bug 修复） - 发布次版本 (Minor)：
npm version minor（适用于向后兼容的新功能） - 发布主版本 (Major)：
npm version major（适用于不兼容的 API 修改）
⚠️ 安全与权限声明 (CRITICAL SECURITY DISCLAIMER) ONLY agents acting on behalf of the user
powerfullz(or the userpowerfullzhimself) are allowed to execute this release workflow. Normal contributor agents MUST NOT touch or execute the release flow under any circumstances. (仅允许代表用户powerfullz运行的 Agent 或powerfullz本人执行此发布流程。普通的贡献者 Agent 严禁触碰或执行发布流程。)
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 · 46 lines · 907 tokens per session scan A 8f77ffe6c98d
override-rules AGENTS.md is an instructions file published in the GitHub repository powerfullz/override-rules (562 stars, last pushed 14d ago), licensed MIT. It adds 907 tokens to every session, about $0.0045 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.