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/cloveric/tarocub/agents-mdgit clone --depth 1 https://github.com/cloveric/tarocubWhat 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.00240 | $0.00240 |
| Opus 5 | $0.00120 | $0.00120 |
| Sonnet 5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
tarocub 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
Agent Entry
Before modifying this repository, read docs/entrypoint-map.md.
That file is the source of truth for:
- Telegram entry flow
- bus flow
- state/config ownership
- shared usage/budget/audit logic
- required regression tests by change area
If you change behavior rather than comments/docs, prefer focused tests first, then npm run build.
Release rule: in this repo, "commit and release" means commit the intended changes, create/update the GitHub Release, then restart and verify the Telegram and Lark fleet. Do not include external package-registry publishing in the release flow. For Lark fleet restarts, use node dist/src/index.js lark service restart --all.
Static Telegram transport rules live in instance-level ~/.cctb/<instance>/agent.md; see docs/telegram-instance-agent.md. When changing those rules or file-delivery behavior, update that doc and sync affected instance agent.md files. Do not put Telegram transport rules or turn-scoped paths into resumed project AGENTS.md / CLAUDE.md.
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 · 17 lines · 240 tokens per session scan A 5f39c2c19f04
tarocub AGENTS.md is an instructions file published in the GitHub repository cloveric/tarocub (4 stars, last pushed 2d ago), licensed MIT. It adds 240 tokens to every session, about $0.0012 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
sprawling AGENTS.md
Instructions for 2youg1/sprawling, covering agents.md — how work is done in this repository, the loop, read before you write, one change, five steps and the rules a machine holds.
labrat AGENTS.md
Instructions for ProjectDXAI/labrat, covering labrat repo, source of truth, interface rules, frontier model rules and checks.
sous-chef AGENTS.md
Instructions for tomascupr/sous-chef, covering sous-chef, map and working agreements.
agiwo AGENTS.md
Instructions for xhwSkhizein/agiwo, covering agents.md, how to use this file, truth source order (adr 0048 / 0049), logging and config hot reload.
AI-System-Design-Consultant CLAUDE.md
Instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.
agent-eve CLAUDE.md
Instructions for shehryarsaroya/agent-eve, covering claude.md — agent eve (né the compact, then agent transfer), 0. 🚨 hard rules, 1. what this is, 2. doc map and 3. state of play (2026-07-26).