tarocub
AGENTS.md20 starsChanged 6 months agoMITView on GitHub
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…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cloveric/cc-telegram-bridgeword for word, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cloveric/cc-telegram-bridge★ 20100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- lark-bot-permissionsSkill
- scraplingSkill
- tarocub-service-opsSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Before modifying this repository, read docs/entrypoint-map.md.
- Very specific: line 12
If you change behavior rather than comments/docs, prefer focused tests first, then npm run build.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Stable Telegram transport rules are bridge-owned and injected at runtime from src/telegram/agent-instructions.ts; see docs/telegram-instance-agent.md. Instance-level ~/.cctb/<instance>/agent.md is user-owned and should contain only persona/preferences. Do not put bridge transport rules or turn-scoped paths into instance agent.md or resumed project AGENTS.md / CLAUDE.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.