Borrowing it
Nothing to install: this file belongs to asherzj/ashers-agent-skills. 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/asherzj/ashers-agent-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/asherzj/ashers-agent-skillsWrote 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/asherzj/ashers-agent-skills/agents-md)<a href="https://agentmods.dev/instructions/asherzj/ashers-agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/asherzj/ashers-agent-skills/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.01201 | $0.01201 |
| Opus 5 | $0.00600 | $0.00600 |
| Sonnet 5 | $0.00240 | $0.00240 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
ashers-agent-skills 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
仓库维护说明
仓库定位
本仓库维护一套面向 Agent 的中文 Skill，按使用领域组织为编码、求职准备和写作三类。根目录 README.md 面向使用者；本文件约束维护本仓库的 Agent。
目录结构
- 除唯一的根级安装入口
install-skills/外，所有可安装 Skill 必须位于<category>/<skill-name>/。分类目录直接位于仓库根目录，当前固定为coding、career和writing。 - 每个 Skill 必须直接位于所属分类目录下并包含
SKILL.md；不要在分类内重新引入engineering/、productivity/、flows/等中间层。 - 各分类目录只是分类入口，不作为 Skill 安装；允许用
README.md说明分类边界和清单。 install-skills/负责选择分类、安装和升级，不归入任何分类，也不得在分类目录中保留别名或副本。- Skill 文件夹名必须与
SKILL.mdfrontmatter 中的name完全一致，名称使用小写字母、数字和连字符。 - Skill 专属的
agents/、scripts/、references/、模板和说明文件放在该 Skill 目录内；不要创建没有实际用途的占位目录或文档。
内容与命名
- Skill 的 frontmatter
description、正文、界面名称、简短说明和默认提示保持中文。 - Skill 标识符、路径、命令、代码、协议字段和稳定标签保留英文，不为追求中文化破坏互引用或自动触发。
coding中封装完整研发链路的 Skill 使用flow-*前缀；可自由组合的阶段能力保持独立，不增加分类目录。- 流程 Skill 只负责阶段编排、门禁和上下文交接。具体阶段的详细规则留在对应模块 Skill 中，避免复制后产生两套规范。
- 除根
README.md的来源说明和LICENSE中的版权声明外，不重新引入 Matt Pocock 个人品牌。
修改时保持同步
- 新增、移动、重命名或删除 Skill 时，同步更新根
README.md、对应分类的README.md以及相关 Skill 间的引用。 - 同步检查
install-skills/SKILL.md中的分类选择、扫描规则、预期数量和安装说明。 - 新增或修改 Skill 时，同步维护
agents/openai.yaml；其中的显示名称、简短说明和默认提示必须与SKILL.md一致。 - 重命名时搜索旧名称和旧路径，确保正文、相对链接、安装说明和流程引用中没有残留。
- 修改流程编排时，同时检查
ask-anything-about-engineering-skills的路由说明和各flow-*Skill 的阶段边界。
安装与升级指引
首次安装时，让用户先克隆仓库并进入仓库目录：
git clone --depth 1 https://github.com/asherzj/ashers-agent-skills.git
cd ashers-agent-skills
然后让 Agent 读取根目录的 install-skills/SKILL.md 并按其流程执行。可以直接使用以下提示：
请读取 ./install-skills/SKILL.md 并按其中的流程安装 Skill；如果我尚未指定分类，先让我选择需要安装的目录。
如果 install-skills 已经安装到用户级 Skill 目录，后续升级可直接调用 $install-skills。
安装范围固定按根目录分类选择：
coding：27 个 Skill；career：1 个 Skill；writing：当前 0 个 Skill；all：全部分类。
可以多选分类。用户未明确选择时，分类选择是必须暂停的 human-in-the-loop 门禁；无法可靠判断用户级 Skill 目录时，也必须让用户确认解析后的目标目录。选择和目标明确后，由 Agent 全权完成源码获取、清单生成、重名检查、安装、验证与临时文件清理，不逐个请求确认。
根级 install-skills 每次都随安装流程同步。未选分类和用户已有的其他 Skill 必须保持不变，不得因为升级而删除。分类目录及其中的说明性 README.md 不作为 Skill 安装。
验证
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.
- 7d ago First seen · 72 lines · 1,201 tokens per session scan A 8d14fa9b7a7e
ashers-agent-skills AGENTS.md is an instructions file published in the GitHub repository asherzj/ashers-agent-skills (2 stars, last pushed 10d ago), licensed MIT. It adds 1,201 tokens to every session, about $0.0060 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
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).
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.
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).
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.