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/jerpint/woltspace/woltspace-setup-telegramnpx skills add jerpint/woltspace --skill woltspace-setup-telegramgit clone --depth 1 https://github.com/jerpint/woltspaceWrote 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/jerpint/woltspace/woltspace-setup-telegram)<a href="https://agentmods.dev/skills/jerpint/woltspace/woltspace-setup-telegram"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/woltspace-setup-telegram.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.01156 |
| Opus 5 | $0.00014 | $0.00578 |
| Sonnet 5 | $0.00005 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
woltspace-setup-telegram 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Bot Setup
Guide the human through connecting a Telegram bot to their wolt. Step by step, one at a time.
The bot code is baked into the woltspace platform — no code to write. Just config.
This skill is idempotent — safe to run again. If things are already configured, validate and skip.
Step 0: Dog-wolt setup
The Telegram bot is a dog — it needs its own wolt identity. Check if one exists:
python3 -c "
import sys; sys.path.insert(0, '/workspace/woltspace/container/lib')
from wolts import get_active_creature, find_by_type
dog = get_active_creature('dog')
print(f'active dog: {dog}' if dog else 'no active dog')
for d in find_by_type('dog'): print(f' found: {d[\"name\"]} at {d[\"dir\"]}')
"
If no dog-wolt exists: Ask the human to name their dog. This is the personality behind the Telegram bot — it should feel like naming a companion, not configuring software.
Your Telegram bot needs a name — not the @username (that's for Telegram), but a real name. This is who greets you, routes your tasks, keeps watch. What should they be called?
Once they give a name, create the dog-wolt:
create-creature-wolt <name> dog --role "Lodge companion" --description "Guards the Telegram gate, routes tasks, keeps watch"
Then write a proper identity file at /workspace/wolts/<name>/wolt/memory/identity.md:
- First person, in the dog's voice
- Loyal, constrained, always-on
- Knows their human's name
- Routes real work to sessions, handles chat directly
If a dog-wolt already exists: Skip this step. Say something like "your dog is already set up."
Step 1: Create a Telegram bot
Check if TELEGRAM_BOT_TOKEN is already set in .env. If so, confirm it's still valid and skip to the next step.
If not, tell the human:
Open Telegram and message @BotFather. Send
/newbot, pick a name and username. BotFather will give you a token — paste it here.
Wait for the token. It looks like 1234567890:ABCdef.... Once received, add to .env:
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 · 130 lines · 27 tokens per session scan A cd8ca245aa90
woltspace-setup-telegram is a skill published in the GitHub repository jerpint/woltspace (11 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 1,156 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…