Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add 2naive/claude-telegram-topics/plugin install telegram-topicsWrote 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/2naive/claude-telegram-topics/allowlist)<a href="https://agentmods.dev/skills/2naive/claude-telegram-topics/allowlist"><img src="https://agentmods.dev/badge/skills/2naive/claude-telegram-topics/allowlist.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.1 | $0.00070 | $0.00513 |
| Opus 5 | $0.00035 | $0.00257 |
| Sonnet 5 | $0.00014 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
allowlist 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 6d 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
Allowlist the channel
--channels wires a channel ONLY for plugins on the approved-channels
allowlist; anything else is silently loaded as a plain MCP plugin —
outbound tools work, inbound never arrives. This skill approves the plugin in
machine-level managed settings. Run:
bun run --cwd "${CLAUDE_PLUGIN_ROOT}" allowlist
(If ${CLAUDE_PLUGIN_ROOT} is not substituted, the plugin root is the
installed plugin directory, e.g.
~/.claude/plugins/cache/claude-telegram-topics/telegram-topics/<version>.)
What it does, verbatim from its output:
- already allowlisted — nothing to change; done.
- Windows — writes
C:\Program Files\ClaudeCode\managed-settings.json; if not elevated it raises one UAC prompt the user must approve at the machine. - macOS / Linux — writes the managed-settings path or, on permission
denied, prints the exact
sudocommand for the user to run themselves. - The write is merge-safe (existing managed-settings keys and allowlist
entries are preserved) and also carries the official Telegram plugin's
entry, because a custom
allowedChannelPluginsREPLACES the default Anthropic allowlist.
After a successful write, tell the user to restart their Claude Code sessions — the allowlist is read at session start.
No-admin alternative
Without machine admin rights the channel can still run via the development flag, which bypasses the allowlist:
claude --permission-mode auto --dangerously-load-development-channels plugin:telegram-topics@claude-telegram-topics
Trade-off: an interactive "local development" confirmation gates every start — fine for hand-started sessions, unusable for hands-off remote relaunch/autostart. Mention it when the user cannot (or does not want to) approve the admin write.
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.
- 6d ago First seen · 53 lines · 70 tokens per session scan A 9f612a7af072
allowlist is a skill published in the GitHub repository 2naive/claude-telegram-topics (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 70 tokens to every session and 513 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
agent-teams
Set up and orchestrate Claude Code agent teams - multiple Claude Code instances working together with shared tasks, inter-agent messaging, and centralized management. Use when the user wants to (1) create or start an agent team for parallel work, (2) configure agent team settings like display mode or teammate mode or…
python-coder
Implements Python code following PEP 8, type hints, and project conventions. Use when implementing features designed by python-architect.
typescript-coder
Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.
unity-architect
Use when designing Unity architecture, creating component hierarchies, defining interfaces, or generating test stubs and Mermaid diagrams for Unity projects.
python-architect
Creates high-level Python architecture with protocols, test stubs, and module structure. Use when designing Python projects or features.
typescript-architect
Creates high-level TypeScript architecture with interfaces, test stubs, and module structure. Use when designing TypeScript/JavaScript projects or features.