agentmods.dev

mcp-telegram-agent: Command for Claude Code

.cursor/commands/setup-mcp-telegram-agent.md

setup-mcp-telegram-agent is a command for Claude Code, Cursor from tecnomanu/mcp-telegram-agent. It costs 0 tokens per session (346 once invoked), scanned A, original, MIT.

An onboarding command for connecting a coding agent to a Telegram bot through an MCP server, a tool interface that lets the agent use external services. It guides setup, verifies the Telegram chat, updates configuration, and sends a test message.

In plain words
What is it for?
Use it to configure mcp-telegram-agent, link a bot using its Telegram token, confirm the destination chat, and test Telegram notifications.
Why use it?
It removes the need to manually install the server, exchange setup codes, find the correct chat ID, and edit configuration files. It also checks that the connection works.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md). Also seen: mentions AGENTS.md.

This is tecnomanu/mcp-telegram-agent's own configuration. It tells Claude Code and Cursor how to work on mcp-telegram-agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-telegram-agent configures →

not rated 0repo 4mo ago A scan 0 tokens original MIT
View source ↗ tecnomanu/mcp-telegram-agent
Reuse

Borrowing it

Nothing to install: this file belongs to tecnomanu/mcp-telegram-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tecnomanu/mcp-telegram-agent/main/.cursor/commands/setup-mcp-telegram-agent.md
Clone the repo
git clone --depth 1 https://github.com/tecnomanu/mcp-telegram-agent

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for setup-mcp-telegram-agent

README.md
[![agentmods](https://agentmods.dev/badge/commands/tecnomanu/mcp-telegram-agent/setup-mcp-telegram-agent/github.svg)](https://agentmods.dev/commands/tecnomanu/mcp-telegram-agent/setup-mcp-telegram-agent)
Your own site
<a href="https://agentmods.dev/commands/tecnomanu/mcp-telegram-agent/setup-mcp-telegram-agent"><img src="https://agentmods.dev/badge/commands/tecnomanu/mcp-telegram-agent/setup-mcp-telegram-agent/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.

agentmods 80×15 button for setup-mcp-telegram-agent

Your own site · 80×15
<a href="https://agentmods.dev/commands/tecnomanu/mcp-telegram-agent/setup-mcp-telegram-agent"><img src="https://agentmods.dev/badge/commands/tecnomanu/mcp-telegram-agent/setup-mcp-telegram-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 346 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00346
Opus 5 $0.00000 $0.00173
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00035

Measured 8d ago against content hash 4df172e829cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

setup-mcp-telegram-agent 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.

.cursor/commands/setup-mcp-telegram-agent.md · 33 lines

What it actually says

Setup MCP Telegram Agent

Run a complete onboarding flow for mcp-telegram-agent. Follow repository rules in AGENTS.md first.

Execute this checklist

  1. Ensure MCP server is installed/active first:
    • command: npx
    • args: ["-y", "mcp-telegram-agent"]
  2. Ask the user for BOT_TELEGRAM_TOKEN.
    • If they do not have a bot yet, send them to: https://telegram.me/BotFather#
    • If client supports secure input (elicitation), you can omit token args and let MCP prompt it.
  3. Call tool telegram_onboarding_prepare using that token.
  4. Extract setupCode from the tool output.
  5. Ask the user to press Start if needed, then send <setupCode> as a plain message to their bot in Telegram.
  6. Wait for user confirmation.
  7. Call tool telegram_onboarding_verify with:
    • same token + setupCode
    • requireChatIdConfirmation=true
    • no expectedChatId yet
  8. Show candidates and ask user to confirm exact chat_id.
  9. Call telegram_onboarding_verify again with confirmed expectedChatId.
  10. Apply the returned MCP JSON snippet into the user's MCP config.
  11. Confirm final status and run one test via send_telegram_notification.
  12. Optional: send telegram_send_control_checkpoint so user can reply with continue/stop/rerun commands.

Output style

  • Keep responses concise.
  • Report exact chat_id and test result.
  • Mask token when echoing it in chat output.
Changes

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.

  1. 8d ago First seen · 33 lines · 0 tokens per session scan A 4df172e829cc

Subscribe to this mod's changes

setup-mcp-telegram-agent is a command published in the GitHub repository tecnomanu/mcp-telegram-agent (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 346 tokens. 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.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens