openclaw-cn: Instructions file for Codex

AGENTS.md

openclaw-cn AGENTS.md is an instructions file for Codex, OpenCode from YeSongYun/openclaw-cn. It costs 5,961 tokens per session, scanned B, original, MIT.

A set of repository instructions for working on the OpenClaw codebase, including its structure, documentation, translations, virtual-machine operations, and GitHub communication rules. AGENTS.md is a file that tells coding agents how to work in a repository.

In plain words
What is it for?
Use it when editing OpenClaw code, documentation, translations, security-related work, GitHub issues or pull requests, and development virtual machines.
Why use it?
It prevents common project-specific mistakes, such as using the wrong file paths, formatting GitHub comments incorrectly, or skipping required security guidance.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md; built for openclaw.

This is YeSongYun/openclaw-cn's own configuration. It tells Codex and OpenCode how to work on openclaw-cn itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openclaw-cn configures →

Reuse

Borrowing it

Nothing to install: this file belongs to YeSongYun/openclaw-cn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/YeSongYun/openclaw-cn/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/YeSongYun/openclaw-cn

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for openclaw-cn AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yesongyun/openclaw-cn/agents-md.svg)](https://agentmods.dev/instructions/yesongyun/openclaw-cn/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/yesongyun/openclaw-cn/agents-md"><img src="https://agentmods.dev/badge/instructions/yesongyun/openclaw-cn/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 5,961 This file is loaded in full into every session.
When invoked 5,961 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.05961 $0.05961
Opus 5 $0.02981 $0.02981
Sonnet 5 $0.01192 $0.01192
Haiku 4.5 $0.00596 $0.00596

Measured 7d ago against content hash c019f70ccb75, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

openclaw-cn AGENTS.md scanned grade B with 1 finding 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Update: `sudo npm i -g openclaw@latest` (global install needs root on `/usr/lib/node_modules`).
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 257 lines

How it starts

The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

  • Repo: https://github.com/openclaw/openclaw
  • In chat replies, file references must be repo-root relative only (example: extensions/bluebubbles/src/channel.ts:80); never absolute paths or ~/....
  • GitHub issues/comments/PR comments: use literal multiline strings or -F - <<'EOF' (or $'...') for real newlines; never embed "\n".
  • GitHub comment footgun: never use gh issue/pr comment -b "..." when body contains backticks or shell chars. Always use single-quoted heredoc (-F - <<'EOF') so no command substitution/escaping corruption.
  • GitHub linking footgun: don’t wrap issue/PR refs like #24643 in backticks when you want auto-linking. Use plain #24643 (optionally add full URL).
  • Security advisory analysis: before triage/severity decisions, read SECURITY.md to align with OpenClaw's trust model and design boundaries.

Project Structure & Module Organization

  • Source code: src/ (CLI wiring in src/cli, commands in src/commands, web provider in src/provider-web.ts, infra in src/infra, media pipeline in src/media).
  • Tests: colocated *.test.ts.
  • Docs: docs/ (images, queue, Pi config). Built output lives in dist/.
  • Plugins/extensions: live under extensions/* (workspace packages). Keep plugin-only deps in the extension package.json; do not add them to the root package.json unless core uses them.
  • Plugins: install runs npm install --omit=dev in plugin dir; runtime deps must live in dependencies. Avoid workspace:* in dependencies (npm install breaks); put openclaw in devDependencies or peerDependencies instead (runtime resolves openclaw/plugin-sdk via jiti alias).
  • Installers served from https://openclaw.ai/*: live in the sibling repo ../openclaw.ai (public/install.sh, public/install-cli.sh, public/install.ps1).
  • Messaging channels: always consider all built-in + extension channels when refactoring shared logic (routing, allowlists, pairing, command gating, onboarding, docs).
    • Core channel docs: docs/channels/
    • Core channel code: src/telegram, src/discord, src/slack, src/signal, src/imessage, src/web (WhatsApp web), src/channels, src/routing
    • Extensions (channel plugins): extensions/* (e.g. extensions/msteams, extensions/matrix, extensions/zalo, extensions/zalouser, extensions/voice-call)
  • When adding channels/extensions/apps/docs, update .github/labeler.yml and create matching GitHub labels (use existing channel/extension label colors).

Read the full file on GitHub · 257 lines

Changes

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.

  1. 7d ago First seen · 257 lines · 5,961 tokens per session scan B c019f70ccb75

Subscribe to this mod's changes

openclaw-cn AGENTS.md is an instructions file published in the GitHub repository YeSongYun/openclaw-cn (56 stars, last pushed 3mo ago), licensed MIT. It adds 5,961 tokens to every session, about $0.0298 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens