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/codeinfinity1/stram/telegram-operationsnpx skills add CodeInfinity1/Stram --skill telegram-operationsgit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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.00027 | $0.00992 |
| Opus 5 | $0.00014 | $0.00496 |
| Sonnet 5 | $0.00005 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
telegram-operations 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Operations
Tool Map
channel_manifestchannel_setup_requirementschannel_setup_savechannel_setup_statuschannel_doctorchannel_listener_statuschannel_listener_tickchannel_webhook_ingestchannel_message_preparechannel_action_preparechannel_message_sendchannel_outbox
Use this skill when Telegram bot setup, Telegram groups, topics, media conversion, or Telegram sends are involved.
Setup
- Create a bot with BotFather.
- Set
TELEGRAM_BOT_TOKEN. - Use numeric chat IDs as
conversation_id. - For supergroups, IDs usually start with
-100. - Save non-secret setup refs with
channel_setup_save. - Run
channel_doctorfortelegram.
Workflow
- Use
channel_setup_requirementsfor Telegram's bot token, numeric chat ID rules, media conversion flag, and listener mode. - Save enabled state, default chat ID, allowlists, group allowlists, and secret references with
channel_setup_save. - Run
channel_setup_status,channel_doctor, andchannel_listener_status. - Use
channel_integration_smokefor prepared envelope and dry-run send readiness. - Use
channel_listener_tickfor Telegram long-polling smoke whenTELEGRAM_BOT_TOKENis configured. - Use
channel_webhook_ingestfor webhook payload smoke when testing a posted update. - Use
channel_message_prepareandchannel_action_preparebefore any visible message, media send, reaction, topic reply, typing indicator, or read receipt.
Group Rules
For groups:
- Put group chat IDs in group allowlists.
- Put human sender IDs in sender allowlists.
- Do not confuse negative group IDs with user IDs.
- Require mentions by default.
- Disable BotFather privacy mode or make the bot admin only when ambient group messages should be visible.
Topics
Represent topic-scoped conversations with structured metadata or a conversation id convention supplied by the runtime. Keep topic and base group context isolated.
Markdown Images
Telegram supports outbound media. Stram mechanically extracts markdown image syntax from prepared messages when the channel manifest says markdown_image_to_media:true.
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 · 103 lines · 27 tokens per session scan A 11090d0812c2
telegram-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 27 tokens to every session and 992 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.