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/yokingma/weclaws/agents-mdgit clone --depth 1 https://github.com/yokingma/weclawsWhat 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.00696 | $0.00696 |
| Opus 5 | $0.00348 | $0.00348 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
weclaws 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 2d 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
AGENTS.md
This file sets repository-wide rules for coding agents in WeClaws.
Read first: README.md and docs/manuals/README.md.
Working goal: Small, accurate, verifiable changes aligned with the current architecture.
Priority:
- User task
- This file + relevant workspace
PATTERNS.md README.mdanddocs/manuals/*- Existing code patterns
Core rules:
- Supervisor owns runtime; web writes durable intents only.
- SQLite is the source of truth; persistence logic lives in
packages/db. - Use FastAgent only through external contracts.
- Derive bot paths through shared resolvers; do not persist host-specific paths or commit runtime data, secrets, or artifacts.
- Default scope: single-machine, multi-user control plane, one bot per child process, SQLite, Better Auth email/password, per-bot SSE.
Workspace rules:
apps/web: no local process management; intents first, supervisor reconciles.apps/supervisor: consume runtime JSONL and runtime state; child env must be allowlisted.packages/db: narrow semantic APIs; fresh SQLite schema must work; keep migrations in sync.packages/shared: only stable cross-workspace contracts; no compatibility layers unless explicitly required.
Development norms:
- Prefer test-first for new behavior and bug fixes.
- Keep diffs small and focused.
- Use the smallest verification set that covers the change.
- Prefer existing patterns and shared contracts.
- Keep rules concise.
Do not:
- Let web own runtime.
- Treat in-memory state as cross-process truth.
- Add retired-behavior compatibility unless required.
- Present scratch notes as user-facing docs.
- Claim tests, builds, or smoke checks passed unless actually run.
Common commands:
pnpm installpnpm buildpnpm testpnpm typecheckpnpm lintpnpm db:generatepnpm db:migratepnpm --filter @weclaws/web testpnpm --filter @weclaws/supervisor testpnpm --filter @weclaws/db testpnpm --filter @weclaws/shared typecheck
Environment and deployment:
- Node 20.18.1 is recommended.
- Root
.envis for local dev;infra/compose/.envis for Compose. FASTAGENT_SANDBOX_MODEsupportsremoteanddisabled; remote uses owner-specific pool creds.- The default Compose path is the repo-local three-image topology.
- Read the Docker runbook before Compose changes.
Verification:
- Run the smallest matching verification set.
- UI/API changes: web
test/typecheck,buildonly when needed. - Runtime/supervisor changes: supervisor
test/typecheck. - DB changes: db
test/typecheckand migrations when required. - Shared contract changes: affected workspace tests.
- Run
pnpm test:fastagent-contractonly when the required env exists. - Report precisely: passed / not run / blocked.
Documentation:
- Update workspace
CHANGELOG.mdandPATTERNS.mdwhen executable code or behavior changes. - Keep current facts in
README.mdanddocs/manuals/.
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.
- 2d ago First seen · 75 lines · 696 tokens per session scan A a0d4653f1b0d
weclaws AGENTS.md is an instructions file published in the GitHub repository yokingma/weclaws (38 stars, last pushed 3mo ago), licensed MIT. It adds 696 tokens to every session, about $0.0035 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
WxJava AGENTS.md
AGENTS.md instructions for binarywang/WxJava, covering wxjava agent 指南, 适用范围与指令优先级, 项目概览, 开发流程 and 代码风格与兼容性.
WxJava copilot-instructions.md
Copilot instructions for binarywang/WxJava, covering copilot instruction, wxjava - 微信 java sdk 开发说明, 高效开发指南, 前置条件与环境准备 and 引导、构建与校验.
trueforge AGENTS.md
AGENTS.md instructions for truefoundry/trueforge, a project described as: The open-source agent harness - the runtime layer that turns an LLM into a working agent.
ratel AGENTS.md
Instructions for ratel-ai/ratel, covering agents.md — working in the ratel repo, build & test, rust, ts and python (from src/sdk/python/; needs uv).
everruns AGENTS.md
Instructions for everruns/everruns, covering everruns, where guidance lives, norms, gotchas and local dev.
codebay CLAUDE.md
Instructions for khromov/codebay, covering claude.md, what this is, runtime & commands, comments and architecture.