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/six-ddc/ccbot/claude-mdgit clone --depth 1 https://github.com/six-ddc/ccbotWhat 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.00705 | $0.00705 |
| Opus 5 | $0.00352 | $0.00352 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade B, and why
ccbot CLAUDE.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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Or manually in `~/.claude/settings.json`: This is a copy
95% identical to ccbot AGENTS.md — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
ccmux — Telegram bot that bridges Telegram Forum topics to Claude Code sessions via tmux windows. Each topic is bound to one tmux window running one Claude Code instance.
Tech stack: Python, python-telegram-bot, tmux, uv.
Common Commands
uv run ruff check src/ tests/ # Lint — MUST pass before committing
uv run ruff format src/ tests/ # Format — auto-fix, then verify with --check
uv run pyright src/ccbot/ # Type check — MUST be 0 errors before committing
./scripts/restart.sh # Restart the ccbot service after code changes
ccbot hook --install # Auto-install Claude Code SessionStart hook
Core Design Constraints
- 1 Topic = 1 Window = 1 Session — all internal routing keyed by tmux window ID (
@0,@12), not window name. Window names kept as display names. Same directory can have multiple windows. - Topic-only — no backward-compat for non-topic mode. No
active_sessions, no/list, no General topic routing. - No message truncation at parse layer — splitting only at send layer (
split_message, 4096 char limit). - MarkdownV2 only — use
safe_reply/safe_edit/safe_sendhelpers (auto fallback to plain text). Internal queue/UI code calls bot API directly with its own fallback. - Hook-based session tracking —
SessionStarthook writessession_map.json; monitor polls it to detect session changes. - Message queue per user — FIFO ordering, message merging (3800 char limit), tool_use/tool_result pairing.
- Rate limiting —
AIORateLimiter(max_retries=5)on the Application (30/s global). On restart, the global bucket is pre-filled to avoid burst against Telegram's server-side counter.
Code Conventions
- Every
.pyfile starts with a module-level docstring: purpose clear within 10 lines, one-sentence summary first line, then core responsibilities and key components. - Telegram interaction: prefer inline keyboards over reply keyboards; use
edit_message_textfor in-place updates; keep callback data under 64 bytes; useanswer_callback_queryfor instant feedback.
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 · 60 lines · 705 tokens per session scan B 6a699a0daa05
ccbot CLAUDE.md is an instructions file published in the GitHub repository six-ddc/ccbot (273 stars, last pushed 1mo ago), licensed MIT. It adds 705 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 95% identical to ccbot AGENTS.md, differing in 14 lines, and is treated as a copy.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.