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 raulvidis/openclaw-multi-agent-kit --skill telegram-topic-setupgit clone --depth 1 https://github.com/raulvidis/openclaw-multi-agent-kitWrote 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/raulvidis/openclaw-multi-agent-kit/telegram-topic-setup)<a href="https://agentmods.dev/skills/raulvidis/openclaw-multi-agent-kit/telegram-topic-setup"><img src="https://agentmods.dev/badge/skills/raulvidis/openclaw-multi-agent-kit/telegram-topic-setup/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/raulvidis/openclaw-multi-agent-kit/telegram-topic-setup"><img src="https://agentmods.dev/badge/skills/raulvidis/openclaw-multi-agent-kit/telegram-topic-setup.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 Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00037 | $0.00466 |
| Opus 5.5 | $0.00015 | $0.00186 |
| Sonnet 5.5 | $0.00007 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
telegram-topic-setup 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 1mo 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.
What it actually says
Install
Copy to agents/<orchestrator>/skills/telegram-topic-setup/SKILL.md. Requires a Telegram supergroup with forum mode enabled and bot admin permissions.
Telegram Topic Setup Skill
Topic Creation
Use the topic-create action to create a new forum topic:
action: topic-create
channel: telegram
target: telegram:<chatId>
name: <topic-name>
icon_custom_emoji_id: <emoji-id>
Returns a topicId on success.
Initial Message
After creating a topic, send a first message immediately using:
threadId: <topicId>
Telegram may not display the topic in the list until the first message is posted.
Icon Selection
Only custom emoji IDs from Telegram's forum topic sticker set are valid as icon_custom_emoji_id. There are 38 valid IDs. Common ones:
| Emoji | ID |
|---|---|
| 💻 | 5350554349074391003 |
| 🔥 | 5312241539987020022 |
| 📈 | 5350305691942788490 |
| 💡 | 5312536423851630001 |
If an invalid ID is used, Telegram ignores it and assigns a default icon.
Recording Topic IDs
Capture every returned topicId and record it in SUPERGROUP-MAP.md under the corresponding team and agent entry. This mapping drives config generation and agent routing.
Binding Agents
Wire each topic to an agent in openclaw.json:
{
"topics": {
"<TOPIC_ID>": {
"requireMention": true,
"enabled": true
}
}
}
Rules:
- Multi-agent topics: all bots must have
requireMention: true - Single-agent topics: the sole agent can use
requireMention: false - Orchestrator: set
enabled: falseon topics owned by other agents
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.
- 1mo ago First seen · 73 lines · 37 tokens per session scan A b70e6ff46db9
telegram-topic-setup is a skill published in the GitHub repository raulvidis/openclaw-multi-agent-kit (396 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 466 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.