Borrowing it
Nothing to install: this file belongs to trxxxxkov/chxxxxbot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/trxxxxkov/chxxxxbot/main/CLAUDE.mdgit clone --depth 1 https://github.com/trxxxxkov/chxxxxbotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/trxxxxkov/chxxxxbot/claude-md)<a href="https://agentmods.dev/instructions/trxxxxkov/chxxxxbot/claude-md"><img src="https://agentmods.dev/badge/instructions/trxxxxkov/chxxxxbot/claude-md.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.02021 | $0.02021 |
| Opus 5 | $0.01010 | $0.01010 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
chxxxxbot CLAUDE.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 8d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working with this repository.
Project Overview
Telegram bot with multi-provider LLM integration (Claude, Google Gemini). Microservices architecture with Docker Compose.
Stack: Python 3.12+, aiogram 3.25+, PostgreSQL 16, Redis 7, Anthropic SDK, Google GenAI SDK
File Structure
chxxxxbot/
├── bot/ # Main application container
│ ├── main.py # Entry point
│ ├── config.py # Settings, model registry, system prompt
│ ├── telegram/
│ │ ├── handlers/ # Message handlers (claude.py is main)
│ │ ├── pipeline/ # Unified message processing
│ │ │ ├── handler.py # Entry point, batching
│ │ │ ├── processor.py # Core processing logic
│ │ │ ├── normalizer.py # Message normalization
│ │ │ ├── models.py # ProcessedMessage, UploadedFile
│ │ │ ├── queue.py # Message queue management
│ │ │ └── tracker.py # Upload tracking
│ │ ├── middlewares/ # Logging, database, balance check
│ │ ├── keyboards/ # Inline/reply keyboards
│ │ └── loader.py # Bot initialization
│ ├── core/
│ │ ├── base.py # Abstract LLMProvider interface
│ │ ├── provider_factory.py # Provider factory (lazy singletons)
│ │ ├── claude/ # Claude API client, context manager
│ │ ├── google/ # Google Gemini API client
│ │ ├── tools/ # Tool implementations
│ │ ├── message_queue.py # 200ms batching for split messages
│ │ └── pricing.py # Cost calculation (multi-provider)
│ ├── services/ # Payment, balance, topic naming services
│ ├── db/
│ │ ├── models/ # User, Chat, Thread, Message, Payment, etc.
│ │ └── repositories/ # CRUD operations
│ ├── cache/ # Redis caching layer
│ └── tests/ # 2000+ tests
├── postgres/ # PostgreSQL + Alembic migrations
├── redis/ # Redis cache
├── grafana/ # Monitoring dashboards + alerts
├── prometheus/ # Metrics collection
├── loki/ + promtail/ # Log aggregation
├── secrets/ # Docker secrets (.gitignore)
└── docs/ # Architecture documentation
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.
- 8d ago First seen · 208 lines · 2,021 tokens per session scan A 5b9a03bacbb8
chxxxxbot CLAUDE.md is an instructions file published in the GitHub repository trxxxxkov/chxxxxbot (5 stars, last pushed 2mo ago), licensed MIT. It adds 2,021 tokens to every session, about $0.0101 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.