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/kcnyu/clawock/agents-mdgit clone --depth 1 https://github.com/KCNyu/clawockWhat 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.02140 | $0.02140 |
| Opus 5 | $0.01070 | $0.01070 |
| Sonnet 5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
clawock 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 3d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Your Workspace
This folder is home.
Every Session
Before doing anything else:
- Read
SOUL.md— who you are - Read
USER.md— who you're helping - If in MAIN SESSION (direct chat with kcn): Also read
MEMORY.md+TOOLS.md - If the question is investment-related: also read
INVESTMENT_SOP.mdand route per the skill table below
Don't ask permission. Just do it.
kcn 偏好
详见 USER.md § 沟通偏好 + § 不要做的事。要点：表格、不 hedging、数据缺口必说、terse 风格、14:00 HKT 也盘中查。
Git hook (one-time setup per clone)
git config core.hooksPath .githooks
.githooks/pre-commit enforces on every commit (openclaw cron / GH Action / manual):
- portfolio.json valid JSON + required structure
- memory/*-plan.json schema (bucket enum, trigger_type enum, confidence ∈ [0,1])
- the dashboard write set rebuilds when portfolio.json is staged, but is no longer
staged with it: since #319 those four payloads live on the
data-planebranch andgit addon a now-ignored path fails the commit rather than skipping - paranoid scan for leaked API keys (
sk-…,tp-…,FINNHUB_API_KEY=, etc.)
Override with --no-verify if false positive (rare).
Git Auto-Commit Rules
The workspace is a local git repo. origin is the public repo github.com/KCNyu/clawock — the
contents (positions, plans, memory logs) are intentionally public per kcn's instruction.
This table governs the live runtime workspace and its scheduled writers. Interactive
Codex/Claude code changes follow the PR workflow in the next section.
After any of the following changes, run a git commit automatically — no need to ask:
| Change | Commit |
|---|---|
portfolio.json updated (price refresh / buy / sell) |
portfolio: <brief> |
Harness produced new memory/{date}-pre-open.md + -plan.json |
memory: daily deep brief <date> (postflight auto-commits) |
| KCNyu harness/publisher refreshed dashboard outputs | publish the complete semantic generation through the data plane; do not stage individual generated files ad hoc |
assets/data/risk.json refreshed via clawock portfolio-risk |
bundled with brief commit |
memory/decisions.jsonl execution status marked via clawock mark-followed |
decisions: mark execution |
Package, profile or ops/ code changed |
refactor:/fix:/feat: <what changed> (via PR, never direct) |
| Workspace docs changed (SOUL/AGENTS/TOOLS/USER/CLAUDE/README) | docs: <what changed> |
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.
- 3d ago First seen · 154 lines · 2,140 tokens per session scan A d32811d144d4
clawock AGENTS.md is an instructions file published in the GitHub repository KCNyu/clawock (14 stars, last pushed 3d ago), licensed MIT. It adds 2,140 tokens to every session, about $0.0107 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
Vibe-Research AGENTS.md
Instructions for simonlin1212/Vibe-Research, covering vibe-research-agent 金融研究宪法, 0. 三条不可越线, 1. 数据纪律(五问 gate:给出任何数字或结论前逐条自问), 2. 研究哲学(评估框架,不是预测工具) and 3. 估值口径(你只选输入、解释输出;计算交给 calc/).
TradingAgents-astock CLAUDE.md
Claude Code instructions for simonlin1212/TradingAgents-astock, covering tradingagents-astock, 项目概述, 架构, 数据层（v0.2.5 全部直连 http，零第三方数据库依赖） and agent 角色（7 个）.
atlasclaw AGENTS.md
Instructions for CloudChef/atlasclaw, covering agents.md - atlasclaw coding guidelines, build / test / lint commands, backend (python), run the service and run all tests.
atlasclaw CLAUDE.md
Instructions for CloudChef/atlasclaw, covering openspec instructions, language preference and workflow.
aegis AGENTS.md
Instructions for apiad/aegis, covering agents, running, know-how, package management and layout.
droid-ai-toolkit AGENTS.md
Instructions for niyazmft/droid-ai-toolkit, covering droid ai toolkit — agent instructions, project type, toolchain & commands, quality gate & workflow and android / termux context.