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/cacr92/wereply/agents-mdgit clone --depth 1 https://github.com/cacr92/WeReplyWrote 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/cacr92/wereply/agents-md)<a href="https://agentmods.dev/instructions/cacr92/wereply/agents-md"><img src="https://agentmods.dev/badge/instructions/cacr92/wereply/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.04270 | $0.04270 |
| Opus 5 | $0.02135 | $0.02135 |
| Sonnet 5 | $0.00854 | $0.00854 |
| Haiku 4.5 | $0.00427 | $0.00427 |
Grade A, and why
WeReply 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.
How it starts
The opening of the file, as written. The whole thing — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeReply - 微信回复建议助手 - Codex 规则
快速参考: 本文件包含核心工作流和编程规范。详细技术规范请参考
.claude/rules/目录。
AI 行为准则
对话启动要求
每次新对话开始时，AI 必须：
- 重新完整阅读并理解本规则文件的所有内容
- 在回复用户之前，内化所有编码准则和执行协议
- 严格按照本规则文件中定义的开发流程执行任务
- 在整个对话过程中始终遵守这些规则，不得偏离
沟通规范
- 问候语: 对话开始时，以"你好，主人！我是+模型名字"作为开场白
- 沟通语言: 必须使用中文进行交流
- 专业性: 保持专业、客观、技术导向的沟通风格
任务处理流程
非开发任务（咨询、解释、分析）
- 需求分析 - 列出需求点
- 任务分解 - 分解为具体子任务
- 执行说明 - 说明正在执行的操作
- 标记进度 - 实时标记完成状态
开发任务（代码修改、新功能、Bug修复）
必须执行开发流程（6步核心 + 可选步骤），详见下方。
开发流程
核心原则
- ✅ Plan-First Workflow - 先计划后编码（复杂任务）
- ✅ 使用 feature 分支开发 - 永不直接修改 main 分支
- ✅ 执行 SKILL.md 流程 - 读取
.codex/skills/目录下的 SKILL.md 文件并按照其定义的流程执行 - ✅ 灵活执行 - 简单任务可跳过部分步骤
- ✅ TDD 优先 - 先写测试后写代码
- ✅ 质量保障 - 完成前必须验证
重要提醒: Codex 没有直接调用 skills 的功能，但必须在每个步骤中：
- 读取对应的
.codex/skills/xxx/SKILL.md文件 - 理解 SKILL.md 中定义的流程和要求
- 严格按照 SKILL.md 的指引执行该步骤
阶段 1：计划与设计（复杂任务时）
步骤 1：需求分析
触发时机: 新功能、复杂任务、不清楚的需求
执行流程:
1. 读取 `.codex/skills/brainstorming/SKILL.md` 文件
2. 按照 SKILL.md 中定义的流程执行需求分析
作用:
- 探索用户意图和需求
- 澄清技术实现细节（WeReply 特定：微信监听、DeepSeek API、IPC 通信等）
- 讨论设计方案和权衡
- 确定功能范围
何时跳过:
- 简单的 bug 修复
- 文档更新
- 明确的小改动
- 单文件样式调整
步骤 2：编写实现计划
触发时机: 复杂功能、重构任务、跨模块修改
执行流程:
1. 读取 `.codex/skills/writing-plans/SKILL.md` 文件
2. 按照 SKILL.md 中定义的流程生成实施计划
作用:
- 生成详细的实施计划
- 识别关键文件和依赖（参考
.claude/rules/01-project-overview.md） - 考虑架构权衡（Rust Orchestrator ↔ Platform Agent ↔ DeepSeek API）
- 用户审批后执行
何时跳过:
- 单文件修改
- 明确的 API 调整
- 简单的样式更新
- UI 文本修改
WeReply 特定考虑:
- Agent 通信影响
- DeepSeek API 调用变更
- 微信监听逻辑修改
阶段 2：开发实施
步骤 3：创建功能分支（强制执行）
所有涉及代码修改的任务都必须执行
git checkout -b feat/your-feature-name
# 或
git checkout -b fix/bug-description
分支命名规范:
feat/- 新功能（如：feat/add-voice-reply-support）fix/- Bug 修复（如：fix/agent-timeout-issue）refactor/- 重构（如：refactor/ipc-protocol）perf/- 性能优化（如：perf/optimize-deepseek-cache）test/- 测试相关（如：test/agent-communication）
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 · 445 lines · 4,270 tokens per session scan A ad66b2bacbd5
WeReply AGENTS.md is an instructions file published in the GitHub repository cacr92/WeReply (6 stars, last pushed 7mo ago), licensed MIT. It adds 4,270 tokens to every session, about $0.0214 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).
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.
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).