Borrowing it
Nothing to install: this file belongs to vibeforge1111/spark-telegram-bot. 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/vibeforge1111/spark-telegram-bot/main/CLAUDE.mdgit clone --depth 1 https://github.com/vibeforge1111/spark-telegram-botWrote 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/vibeforge1111/spark-telegram-bot/claude-md)<a href="https://agentmods.dev/instructions/vibeforge1111/spark-telegram-bot/claude-md"><img src="https://agentmods.dev/badge/instructions/vibeforge1111/spark-telegram-bot/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.03131 | $0.03131 |
| Opus 5 | $0.01566 | $0.01566 |
| Sonnet 5 | $0.00626 | $0.00626 |
| Haiku 4.5 | $0.00313 | $0.00313 |
Grade A, and why
spark-telegram-bot 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 7d 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.
This is a copy
94% identical to spark-telegram-bot AGENTS.md — 3 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spark Telegram Bot Agent Ruleset
Repo Role
spark-telegram-bot owns Telegram ingress, concise user-facing composition, command routing, delivery, access prompts, relay metadata, and thin adapters to Builder, CLI, Spawner, memory, and voice evidence.
Canonical truth owned here:
- Telegram command and natural-language ingress behavior
- Telegram-specific access prompts, chat delivery, and reply composition
- relay metadata and metadata-only audit rows emitted by the Telegram adapter
- thin route-context serialization for Builder-owned gates
- Telegram-facing rendering of Builder/CLI/Spawner/Cockpit evidence
This repo does not own:
- Builder RouteConfidenceGateV1, AOC, identity, or memory orchestration
- durable memory storage, memory proof-card truth, or memory mutation authority
- CLI registry, installer, secret storage, or module lifecycle
- Spawner mission execution or provider output bodies
- Cockpit UI action authority or dashboard truth
Start-of-Work Protocol
- Run
git status --short --branch. - Read this file plus
docs/SPARK_SYSTEM_GOVERNANCE_RULESET.md,docs/SPARK_HUMAN_CONVERSATION_QA_MAP.md,docs/SPARK_AGENT_USAGE_RESEARCH_HERMES_OPENCLAW_2026-06-16.md,docs/TURNINTENT_HARNESS_RULESET.md, and the relevant command, route, or adapter doc before edits. - Identify whether the change is Telegram-owned or belongs in Builder, CLI, Spawner, memory, Cockpit, voice, Labs, or Swarm.
- Define the smallest user-visible behavior and stop-ship gate.
- Add focused tests for routing, composition, access, bridge serialization, or relay metadata.
- Keep adapters thin and metadata-only.
- Commit one logical checkpoint and record verification.
Spark-Wide Root-Cause Governance
The canonical repo rule is docs/SPARK_SYSTEM_GOVERNANCE_RULESET.md.
Do not patch Spark behavior with deterministic phrase saves, exact project-name special cases, exact mission-id handling, or reply-text fixes that only make the latest transcript look good. For every nontrivial Spark fix, classify the failure family, identify the earliest owning layer, and prove one natural positive plus one adjacent negative trap.
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.
- 7d ago First seen · 243 lines · 3,131 tokens per session scan A a383b18b2a3f
spark-telegram-bot CLAUDE.md is an instructions file published in the GitHub repository vibeforge1111/spark-telegram-bot (2 stars, last pushed 20d ago), licensed MIT. It adds 3,131 tokens to every session, about $0.0157 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to spark-telegram-bot AGENTS.md, differing in 3 lines, and is treated as a copy.
Other instructions, from other repositories
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).
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.
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).
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.