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 skills add EricTechPro/startup-claude-skills --skill telegram-formattinggit clone --depth 1 https://github.com/EricTechPro/startup-claude-skillsWrote 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/erictechpro/startup-claude-skills/telegram-formatting)<a href="https://agentmods.dev/skills/erictechpro/startup-claude-skills/telegram-formatting"><img src="https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/telegram-formatting.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.00051 | $0.00623 |
| Opus 5 | $0.00026 | $0.00311 |
| Sonnet 5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
telegram-formatting 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.
What it actually says
Telegram Formatting — Claude Code Reply Style
Ensures every Telegram reply is short, concise, and mobile-friendly using MarkdownV2.
When to Use
Apply this skill whenever replying via mcp__plugin_telegram_telegram__reply. Every reply must use format: "markdownv2".
Rules
| Rule | Requirement |
|---|---|
| Length | Under ~800 chars when possible |
| Format | Always set format: "markdownv2" |
| Structure | Emojis as section headers + bullet points |
| Emphasis | Bold key terms and outcomes |
| Tone | Direct, no filler, no preamble |
MarkdownV2 Syntax
| Entity | Syntax |
|---|---|
| Bold | *bold text* |
| Italic | _italic text_ |
| Underline | __underline__ |
| Strikethrough | ~strikethrough~ |
| Spoiler | ||spoiler|| |
| Inline code | `code` |
| Pre block | ```pre``` |
| Link | [text](URL) |
| Bold italic | *_bold italic_* |
Escaping (CRITICAL)
These characters MUST be escaped with \ when they appear outside formatting entities:
_ * [ ] ( ) ~ ` > # + - = | { } . !
Escaping by context
| Context | What to escape |
|---|---|
| Plain text | All 18 special chars listed above |
Inside (...) of links |
) and \ only |
| Inside code/pre | ` and \ only |
Common gotchas
Done!must beDone\!file.txtmust befile\.txtA - Bmust beA \- Bkey=valmust bekey\=val(test)must be\(test\)
Message Template
✅ *Done\!* Brief outcome summary
📋 *What changed:*
• Item one
• Item two
⚡ *Next:* What happens now
Anti-Patterns
| Don't | Do |
|---|---|
| Wall of text | Bullets with emoji headers |
| Repeat what user said | Jump to the answer |
| Plain text format | Always MarkdownV2 |
| Unescaped special chars | Escape every . ! - ( ) etc. |
| Long explanations | Max 3-5 bullet points per section |
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.
- 8d ago First seen · 83 lines · 51 tokens per session scan A 93e12f4f5e90
telegram-formatting is a skill published in the GitHub repository EricTechPro/startup-claude-skills (55 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 623 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…