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/tu11aa/squadrant/telegramnpx skills add tu11aa/squadrant --skill telegramgit clone --depth 1 https://github.com/tu11aa/squadrantWhat 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.00066 | $0.00805 |
| Opus 5 | $0.00033 | $0.00402 |
| Sonnet 5 | $0.00013 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
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 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
squadrant:telegram — Telegram Integration
Squadrant pushes crew lifecycle events to Telegram forum topics and accepts commands back from your phone.
Setup
Run the wizard once (re-run at any time to reconfigure):
squadrant telegram setup
The wizard will:
- Detect an existing bot token and reuse it (or prompt for a new one).
- Wait for a message in your forum supergroup to detect the group id and your user-id.
- Ask whether to enable remote control — say yes to capture your user-id and enable Gate 2 (command execution).
After setup, the bot's /command menu is registered automatically.
Re-run setup if remoteControl ended up OFF (you said no, or it was skipped). Use --reset-token to rotate the bot token.
Two Gates
| Gate | What it checks | Controls |
|---|---|---|
| Gate 1 — chats allowlist | telegram.chats contains the chat id |
Inbound messages are processed |
| Gate 2 — remoteControl + user-id | remoteControl: true AND sender is in telegram.users |
Commands execute |
"⛔ not authorized" means Gate 2 is closed — re-run setup and say yes to remote control.
Reference: docs/diagrams/2026-06-23-telegram-daemon-architecture.html
Register the / Command Menu
Setup registers the menu automatically. To re-register on demand:
squadrant telegram register-commands
If the / autocomplete shows no commands in Telegram, run this command.
Notifications
Live toggle (ephemeral — resets on restart):
squadrant telegram notify <project> on
squadrant telegram notify <project> off
Persistent preferences (written to per-project config):
squadrant telegram notify <project> crew <all|alert_only|done_only|none>
squadrant telegram notify <project> cap <on|off>
squadrant telegram notify --status
Crew notification tiers (cumulative — each includes all below):
| Tier | What fires |
|---|---|
all |
Every crew event (started, blocked, done, failed) |
alert_only |
Blocked + done + failed (default) |
done_only |
Done + failed only |
none |
No crew notifications |
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 · 95 lines · 66 tokens per session scan A d50f1af86488
telegram is a skill published in the GitHub repository tu11aa/squadrant (2 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 805 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.