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 tao12345666333/ankaloop --skill telegram-sendergit clone --depth 1 https://github.com/tao12345666333/ankaloopWrote 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/tao12345666333/ankaloop/telegram-sender)<a href="https://agentmods.dev/skills/tao12345666333/ankaloop/telegram-sender"><img src="https://agentmods.dev/badge/skills/tao12345666333/ankaloop/telegram-sender/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/tao12345666333/ankaloop/telegram-sender"><img src="https://agentmods.dev/badge/skills/tao12345666333/ankaloop/telegram-sender.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 90 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00068 | $0.01236 |
| Opus 5 | $0.00034 | $0.00618 |
| Sonnet 5 | $0.00014 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
telegram-sender scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For actions not covered by this script, use `curl` to call Telegram Bot API directly: How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Sender
Agent-facing guide for outbound Telegram communication.
Assumption: ANKA_TELEGRAM_BOT_TOKEN is already set in the environment.
Required Inputs
chat_id(required) — from inbound message metadata or config- message content (required for send/edit)
- photo source (required for photo): local file path, HTTP(S) image URL, or Telegram
file_id - photo caption (optional, max 1024 characters after Telegram entity parsing)
reply_to_message_id(optional, for threaded reply)message_id(required for edit)
Execution Policy
- If handling a Telegram message and
message_idis known, prefer reply mode (--reply-to). - If source metadata says sender is a bot (
sender_is_bot=true), do not use reply mode; use--source-is-bot --source-username <USERNAME>instead. - For long-running tasks: send an acknowledgment first, then edit it with the final result.
- Use
photowhen the response depends on an image artifact or generated picture. - Prefer local file paths for newly generated images. Use a Telegram
file_idonly when reusing a previously uploaded file. - Keep content concise and action-oriented.
- Use literal newlines in message text and captions.
Active Response Policy
When this skill is in scope, prefer proactive and timely Telegram updates:
- Send immediate acknowledgment for newly assigned tasks
- Send progress updates for long-running operations using message edits
- Send completion notifications when work finishes
- Send failure notifications immediately with cause, impact, and next action
Recommended pattern:
- Send a short acknowledgment reply
- Continue processing
- Edit the acknowledgment with final result (or send a new update if edit fails)
Command Templates
Paths are relative to this skill directory.
# Send message
python ./scripts/telegram_send.py send \
--chat-id <CHAT_ID> \
--message "<TEXT>"
# Reply to a specific message
python ./scripts/telegram_send.py send \
--chat-id <CHAT_ID> \
--message "<TEXT>" \
--reply-to <MESSAGE_ID>
# Bot-source: no direct reply, use @username style
python ./scripts/telegram_send.py send \
--chat-id <CHAT_ID> \
--message "<TEXT>" \
--source-is-bot \
--source-username <USERNAME>
# Edit existing message
python ./scripts/telegram_send.py edit \
--chat-id <CHAT_ID> \
--message-id <MESSAGE_ID> \
--text "<TEXT>"
# Send photo from local path, URL, or Telegram file_id
python ./scripts/telegram_send.py photo \
--chat-id <CHAT_ID> \
--photo "<PATH_OR_URL_OR_FILE_ID>" \
--caption "<OPTIONAL_CAPTION>"
# Reply with a photo
python ./scripts/telegram_send.py photo \
--chat-id <CHAT_ID> \
--photo "<PATH_OR_URL_OR_FILE_ID>" \
--caption "<OPTIONAL_CAPTION>" \
--reply-to <MESSAGE_ID>
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 136 lines · 68 tokens per session scan A cbd33f8c1303
telegram-sender is a skill published in the GitHub repository tao12345666333/ankaloop (48 stars, last pushed 13d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,236 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
review
Review a change for correctness, security, and missing tests.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
recording
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures. Probe capabilities before recording.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.