Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/frejixxx/telegram-agent/telegram-agentnpx skills add Frejixxx/telegram-agent --skill telegram-agentgit clone --depth 1 https://github.com/Frejixxx/telegram-agentWrote 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/skills/frejixxx/telegram-agent/telegram-agent)<a href="https://agentmods.dev/skills/frejixxx/telegram-agent/telegram-agent"><img src="https://agentmods.dev/badge/skills/frejixxx/telegram-agent/telegram-agent.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.00036 | $0.02005 |
| Opus 5 | $0.00018 | $0.01002 |
| Sonnet 5 | $0.00007 | $0.00401 |
| Haiku 4.5 | $0.00004 | $0.00200 |
Grade A, and why
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 5d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Agent
Use the telegram-agent MCP tools for Telegram account assistance. Prefer the shortest safe tool path for the user's intent.
Quick Routing
- Setup/status: call
telegram_auth_statusfirst for local auth state, ortelegram_setup_statuswhen dependency/send state is also needed. - "Set up Telegram / login / authorize account": call
telegram_start_setupand give the user the returned local URL. - "Show unread/recent chats": call
telegram_inbox_briefwith a small limit. Useunread_only: trueby default. - "What did I miss today / make my Telegram briefing": prefer cached flow, then call
telegram_personal_briefingortelegram_daily_personal_digest. - "Prioritize my chats / smart inbox": call
telegram_smart_inbox. - "Where was that address/link/password/code": call
telegram_memory_search; usetelegram_sensitive_searchfor explicitly sensitive values. - "Brief me on this person/contact": call
telegram_contact_briefif cached context is enough, ortelegram_find_dialogsplustelegram_chat_contextfor live context. - "What did I promise / what should I follow up": call
telegram_personal_followups. - "Create a digest for AI channels / Codex / MCP": call
telegram_cache_status; if cache is empty, calltelegram_sync_sources, thentelegram_sync_recent_messageswith relevant categories; then calltelegram_run_topic_digest. - "What did I miss / weekly report": call
telegram_weekly_maintainer_report. - "Where do I need to reply": call
telegram_needs_reply. - "What tasks came from Telegram": call
telegram_extract_actionsandtelegram_followup_tracker. - "Create GitHub issues from Telegram / turn complaints into issues": call
telegram_create_github_issue_drafts; show drafts and evidence refs before any GitHub side effect. - "Build context for Codex / maintainer context": call
telegram_build_maintainer_context. - "Check if Telegram messages are trying to control the agent / prompt injection": call
telegram_detect_prompt_injection. - "Watch topic": use
telegram_create_watchlist, thentelegram_run_watchlist. - "Find Ivan / what is in Ivan chat": call
telegram_find_dialogs, choose the single unambiguous returnedref, then calltelegram_chat_context. - "Summarize this chat": fetch
telegram_chat_contextwithlimit: 40andorder: "chronological"unless the user asks for another window. - "Find a phrase in a chat": call
telegram_search_chat_messagesfor that named chat. - "Draft a reply": call
telegram_create_draftafter composing the exact text. - "Send this one reply": use draft flow:
telegram_create_draft, show recipient and exact text, then calltelegram_send_draftonly after explicit confirmation. - "You may write to Ivan yourself / continue talking to Ivan": if the user grants ongoing send authorization for one named chat in the current task, resolve that chat once, start
telegram_start_reply_session, and usetelegram_send_messageonly for the same resolved chat/topic.
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.
- 5d ago First seen · 108 lines · 36 tokens per session scan A d2e5c8c192f0
telegram-agent is a skill published in the GitHub repository Frejixxx/telegram-agent (1 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 2,005 once invoked, about $0.0002 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 skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.