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 sanjar-x/claudegram --skill tg-replygit clone --depth 1 https://github.com/sanjar-x/claudegramWrote 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/sanjar-x/claudegram/tg-reply)<a href="https://agentmods.dev/skills/sanjar-x/claudegram/tg-reply"><img src="https://agentmods.dev/badge/skills/sanjar-x/claudegram/tg-reply/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/skills/sanjar-x/claudegram/tg-reply"><img src="https://agentmods.dev/badge/skills/sanjar-x/claudegram/tg-reply.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.00028 | $0.00357 |
| Opus 5 | $0.00014 | $0.00179 |
| Sonnet 5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
tg-reply 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tg-reply — 100% identical, 0 lines differ
What it actually says
Ответ на конкретное сообщение в Telegram.
Аргументы пришли как: $ARGUMENTS
Парсинг:
- Чат — первое слово.
- message_id — второе слово, целое число.
- Текст — всё остальное.
Алгоритм:
- Разбери
$ARGUMENTS. Если хотя бы одного из трёх не хватает — попроси уточнить. - Если чат —
@username, преобразуй черезresolve_username. - Подтяни через
get_history(chat=..., limit=1, offset_id=<message_id>+1)сообщение с нужным id и покажи мне его текст и автора — чтобы я убедился, что отвечаешь на правильное. - Покажи мне финальный текст ответа.
- Жди подтверждения «отправляй».
- Вызови
send_message(chat=..., text=<текст>, reply_to=<message_id>). Если в тексте есть символы Markdown без намерения форматирования —parse_mode="none". - Покажи id ответа.
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.
- 9d ago First seen · 33 lines · 28 tokens per session scan A 3a89f1320f9d
tg-reply is a skill published in the GitHub repository sanjar-x/claudegram (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 357 once invoked, about $0.0001 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
dream
Prunes and consolidates the project's auto-memory to keep it minimal — deletes stale, wrong, or redundant memories, merges overlapping ones into existing files, and trims the index. Strong bias against growth: never creates new memory files and never stores new facts. Verifies staleness against the current codebase…
masterplan-detect
Suggest /masterplan import only when legacy masterplan bundle state files (docs/masterplan/ /state.yml at schema 5.x) exist without a matching v8 run. Generic planning artifacts (PLAN.md, TODO.md, ROADMAP.md, design docs, PR task lists) are NOT importable — no /masterplan import can ingest them; mention them only as…
skill-creator
Authors and audits Claude Code skills: frontmatter, directory layout, scope, invocation control, and bundled references or scripts.
git-master
Git expert: atomic commits with style detection, rebase and squash, and history archaeology through blame, bisect and pickaxe.
guide
Open the showreel visual setup guide, or walk the user through installing the plugin's dependencies. Use when the user asks how to set up showreel, install its dependencies, pre-warm the capture motor, install vhs, or says "showreel guide", "setup guide", "como instalar o showreel".
showreel
Use when the user wants to explain or document something visually — annotated screenshots, feature demos, flow GIFs, terminal recordings, before/after comparisons — or says "take a screenshot", "record this flow", "make a gif of", "show how this works", "annotate this page", "demo this feature", "grava um gif", "tira…