Borrowing it
Nothing to install: this file belongs to djbelieny/nova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/djbelieny/nova/main/.claude/skills/telegram-file-sender/SKILL.mdgit clone --depth 1 https://github.com/djbelieny/novaWrote 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/djbelieny/nova/telegram-file-sender)<a href="https://agentmods.dev/skills/djbelieny/nova/telegram-file-sender"><img src="https://agentmods.dev/badge/skills/djbelieny/nova/telegram-file-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/djbelieny/nova/telegram-file-sender"><img src="https://agentmods.dev/badge/skills/djbelieny/nova/telegram-file-sender.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.00064 | $0.00596 |
| Opus 5 | $0.00032 | $0.00298 |
| Sonnet 5 | $0.00013 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
telegram-file-sender 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram File Sender
Send any file as a document attachment to the user's Telegram chat using the Telegram Bot API.
When to Use
- The user asks to "send me" a file, document, report, or any generated output
- The user says "send it to me on Telegram" or "share that file with me"
- After generating a file (PDF, DOCX, XLSX, PPTX, image, etc.) that the user wants delivered
- The user asks to "send this to Telegram" or "attach this"
- Post-call tasks that involve delivering files to the user
Workflow
1. Locate or Generate the File
Identify the file to send. If the file needs to be created first (e.g., a report, document, spreadsheet), generate it using the appropriate skill or tool before proceeding.
2. Send the File
Execute the bundled script to send the file via Telegram:
~/.claude/skills/telegram-file-sender/scripts/send_telegram_file.sh "<file_path>" "<optional_caption>"
Parameters:
file_path(required): Absolute path to the file to sendcaption(optional): A message to display alongside the file (supports Markdown)
Environment variables (loaded automatically from .env):
TELEGRAM_BOT_TOKEN— The bot tokenTELEGRAM_USER_ID— The recipient's chat ID
3. Confirm Delivery
After the script runs, confirm to the user that the file was sent. If it fails, report the error.
Constraints
- Maximum file size: 50MB (Telegram Bot API limit)
- For files larger than 50MB, split or compress the file first, or suggest an alternative delivery method
- The script validates file existence and size before sending
- Captions support Markdown formatting
Examples
Send a generated PDF report:
~/.claude/skills/telegram-file-sender/scripts/send_telegram_file.sh "/tmp/quarterly-report.pdf" "Here's your Q1 report"
Send a spreadsheet without caption:
~/.claude/skills/telegram-file-sender/scripts/send_telegram_file.sh "/path/to/budget.xlsx"
Send a presentation with formatted caption:
~/.claude/skills/telegram-file-sender/scripts/send_telegram_file.sh "/tmp/pitch-deck.pptx" "*Pitch deck* — ready for review"
What ships with it
1 file 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.
- 5d ago First seen · 71 lines · 64 tokens per session scan A 156dcd19e051
telegram-file-sender is a skill published in the GitHub repository djbelieny/nova (5 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 596 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-09-03.
Other skills, from other repositories
intent-recognition
Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother (whether the other primitive appears embedded inside — an agent step inside a workflow, or a workflow invoked as an…
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
one-off-operations
Handles one-off operations: the request is a concrete effect that happens once — export or copy data somewhere, a migration, a backfill, a cleanup — with no trigger, schedule, or reuse intent. The workflow is the vehicle, not the deliverable. Users rarely say "one-off"; infer it from the task's shape. Load before…
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.