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/lanterncx/agent/telegram-notifiernpx skills add LanternCX/Agent --skill telegram-notifiergit clone --depth 1 https://github.com/LanternCX/AgentWhat 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 | $0.00031 | $0.00695 |
| Opus 5 | $0.00015 | $0.00347 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
telegram-notifier 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 2d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
telegram-notifier
What This Skill Does
This skill sends one concise plain-text Telegram reminder when work reaches a point where the user should come back. It is a reminder, not a full report.
When to Use
Use this skill when:
- the work is not an instant reply and the user may have stepped away while waiting
- the result is worth pulling the user back to the current session
- the work is fully complete and ready for the final reply
- the work has reached a natural stopping point and now needs user review, confirmation, or a reply
Do not use this skill when:
- the task is a quick answer or a small fast edit
- the work is still actively in progress and does not need anything from the user yet
- you are tempted to send a progress update or intermediate status
Rules
- Send only when the work is fully complete or paused at a user-facing checkpoint.
- Do not send progress notifications.
- Send only once per task when possible.
- If you retry part of the task, return to the same checkpoint, or send the final reply later, avoid duplicate sends.
- Keep the message short, plain text, and non-sensitive.
- Prefer a single concise line.
- Start from the project prefix in the template, then add a short suffix that tells the user why they should come back now.
- Add exactly one space between the project prefix and the suffix when assembling the final message.
- The suffix may include a small amount of key outcome detail if it helps the user judge urgency.
- The suffix must not be empty or reduced to a vague status word.
- Treat markers like review, confirmation, or reply as direction, not fixed sample sentences.
- Do not include secrets, credentials, private data, or long technical dumps.
- Try sending the reminder first; do not proactively check local config before every send.
- If sending fails, then check whether
skill/telegram-notifier/config.local.envis missing or incomplete. - If config is missing or incomplete, read
references/setup-telegram.mdand run that setup flow.
What ships with it
9 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.
- 2d ago First seen · 57 lines · 31 tokens per session scan A 925a9373a61f
telegram-notifier is a skill published in the GitHub repository LanternCX/Agent (5 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 695 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…