Borrowing it
Nothing to install: this file belongs to laser54/telegram-managed-bot-factory. 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/laser54/telegram-managed-bot-factory/main/AGENTS.mdgit clone --depth 1 https://github.com/laser54/telegram-managed-bot-factoryWrote 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/laser54/telegram-managed-bot-factory/agents-md)<a href="https://agentmods.dev/instructions/laser54/telegram-managed-bot-factory/agents-md"><img src="https://agentmods.dev/badge/instructions/laser54/telegram-managed-bot-factory/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/laser54/telegram-managed-bot-factory/agents-md"><img src="https://agentmods.dev/badge/instructions/laser54/telegram-managed-bot-factory/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00373 | $0.00373 |
| Opus 5.5 | $0.00149 | $0.00149 |
| Sonnet 5.5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
telegram-managed-bot-factory AGENTS.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 1mo 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.
What it actually says
Agent instructions
First rule
Read docs/START_HERE.md and its referenced evidence before making implementation changes. Do not re-run a completed Telegram Managed Bots spike solely because this instruction exists. Block only work that depends on an unproven capability or invalidated evidence. Preserve the proven separate-manager flow and all product invariants; do not turn this repository into a generic bot scaffold.
Product invariants
- User owns the manager bot; Factory owns no hosted manager identity.
- Telegram confirmation is required for every child creation.
- Tokens never enter an LLM prompt, chat, MCP argument/result, CLI argument, YAML, Git, logs, state DB, trace, or fixture.
- Persistent worker owns Telegram update consumption and token retrieval; MCP is only the control plane.
- Child runtime is isolated; only its own secret may reach it.
- Ambiguous external results require reconciliation; no blind retry.
- The default manager bot is separate from the Hermes gateway bot.
Before editing docs or code
- Check
docs/DECISIONS.mdfor unverified assumptions. - Preserve the acceptance tests in
docs/ACCEPTANCE.md. - If an assumption changes, update decision log, specification, and acceptance criteria together.
- Do not claim a protocol/host feature simply because it appears in the MCP specification; prove capability negotiation and a test.
Validation minimum
Before calling a change done, run the relevant unit/integration tests once they exist, inspect git diff, and scan all changed artifacts for secrets or private infrastructure details. Validation does not authorize publication: commit only when included in the requested scope, and obtain explicit user authorization before push, opening a PR, merge, release, submission, or deployment. Before any push/merge that triggers deployment, satisfy the applicable deployment and PROD confirmation gates.
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.
- 1mo ago Changed · +88 tokens per session f2f43a543883
- 1mo ago First seen · 27 lines · 285 tokens per session scan A 2437babd5655
telegram-managed-bot-factory AGENTS.md is an instructions file published in the GitHub repository laser54/telegram-managed-bot-factory (0 stars, last pushed 11d ago), licensed MIT. It adds 373 tokens to every session, about $0.0015 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.