Borrowing it
Nothing to install: this file belongs to lexfrei/mcp-tg. 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/lexfrei/mcp-tg/master/CLAUDE.mdgit clone --depth 1 https://github.com/lexfrei/mcp-tgWrote 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/lexfrei/mcp-tg/claude-md)<a href="https://agentmods.dev/instructions/lexfrei/mcp-tg/claude-md"><img src="https://agentmods.dev/badge/instructions/lexfrei/mcp-tg/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.17982 | $0.17982 |
| Opus 5 | $0.08991 | $0.08991 |
| Sonnet 5 | $0.03596 | $0.03596 |
| Haiku 4.5 | $0.01798 | $0.01798 |
Grade A, and why
mcp-tg CLAUDE.md scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "https://raw.githubusercontent.com/DavidAnson/markdownlint-cli2-action/$(grep -oE 'markdownlint-cli2-action@[0-9a-f]{40}' .github/workflows/docs-validate.yaml | cut -d@ -f2)/package.json" | grep '"markdownlint-c How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Development Guide for mcp-tg
What is this
MCP server for Telegram Client API (MTProto, not Bot API). Uses gotd/td for protocol, exposes 78 tools + resources + prompts via MCP.
Build & Test
go build ./cmd/mcp-tg
go test -race ./...
golangci-lint run
Documentation
User-facing documentation lives in docs/, is built with MkDocs Material (mkdocs.yml) from the fully locked dependencies in requirements-docs.txt (compiled from requirements-docs.in), and follows the same shape as this owner's other docs sites: sections with their own index.md (navigation.indexes), a stylesheet, and a docs.yaml / docs-validate.yaml pair. .github/workflows/docs.yaml publishes to https://mcp-tg.lexfrei.dev on every push to master; .github/workflows/docs-validate.yaml runs markdownlint-cli2 and the same mkdocs build --strict on every PR (TestDocsGates_RunOnPullRequests). README.md is a landing page only — install, quickstart, links — and anything longer belongs on a docs page.
That PR check must be in master's required status checks, and is — today they are Lint, Test, Build (amd64), Build (arm64), Validate Documentation and Release Config. Keep it there: nothing in the workflow graph depends on Validate Documentation, so were it dropped, a PR that breaks the site would merge green, docs.yaml would fail on master, and the site would quietly stop updating with the last good build still served. The list lives in the repository's branch-protection settings, outside version control like the Pages config below, so it can drift from this paragraph with nothing red; gh api repos/lexfrei/mcp-tg/branches/master/protection --jq '.required_status_checks.contexts' is the source of truth. Relative links and anchors inside docs/ ([Peers](peers.md), ../building.md#transport-modes) are checked by that build and by nothing else — TestDocsSiteURLs_ResolveToPages reads absolute URLs only. This is why docs-validate.yaml carries no paths: filter, unlike the reference it is modelled on: GitHub leaves a skipped workflow's check Pending forever and blocks a merge on a required check that never reports, so a filtered workflow can never be required at all.
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.
- 6d ago First seen · 352 lines · 17,982 tokens per session scan A 0b3e27e20af7
mcp-tg CLAUDE.md is an instructions file published in the GitHub repository lexfrei/mcp-tg (5 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 17,982 tokens to every session, about $0.0899 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
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.