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 ogrodev/fsociety/plugin install tyrellWrote 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/commands/ogrodev/fsociety/ty-telegram)<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-telegram"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-telegram/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/commands/ogrodev/fsociety/ty-telegram"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-telegram.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00821 |
| Opus 5.5 | $0.00004 | $0.00328 |
| Sonnet 5.5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
ty-telegram scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.tgstat.ru/channels/search?token=${TGSTAT_TOKEN}&q=<query>&language=en" | \ How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing a Telegram leak channel search for the tyrell data exfiltration plugin.
Step 1 — Profile Gate Check
Telegram hunting for breach intelligence requires at minimum a deep operational profile:
node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-engine.js" telegram --check-profile $ARGUMENTS
If the profile is surface or light, stop and inform the operator:
Telegram breach channel monitoring requires a deep or higher operational profile. Ensure your session identity is appropriately isolated.
Step 2 — Generate Channel and Query List
Run the hunt engine to identify relevant Telegram channels and message search terms:
node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-engine.js" telegram $ARGUMENTS
The script returns: channels (known leak channels, dump sharing groups, and market announcement channels), search_queries, and keywords for message filtering.
Step 3 — Search Public Channels via Telegram Web
For publicly indexed channels, search via available tooling:
- Via MCP web search: Use queries like
site:t.me "<keyword>"or search Telegram web preview for channel names. - Via tgstat/telemetr search APIs (if API key available):
curl -s "https://api.tgstat.ru/channels/search?token=${TGSTAT_TOKEN}&q=<query>&language=en" | \ jq '.response.items[] | {id: .id, username: .username, title: .title, members: .participants_count}' - Via Telegram Bot API (if bot token configured and channel is public):
curl -s "https://api.telegram.org/bot${TELEGRAM_BOT_TOKEN}/getUpdates" | jq '.'
Step 4 — Enumerate Channel Posts
For each identified channel of interest, retrieve recent messages:
- Check the channel's public preview at
https://t.me/s/<channel_username>for recent posts. - Look for pinned messages, file attachments (
.txt,.csv,.sql,.zip), and posts referencing breach sizes or target organizations. - Note message dates, views, and any forwarded origin channels.
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.
- 2mo ago First seen · 93 lines · 10 tokens per session scan A 89b3fc5954dc
ty-telegram is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 821 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
pentest
Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.
pentest-scope
Define or update engagement scope — saves scope to disk without launching a pentest. Can be run before or during an engagement. If a pentest is active and the target changes drastically, warns the operator and suggests a new engagement.
pentest-attacks
Define the attack profile for an engagement — select which attack categories and skills to use. Saves to .pentest-attacks.json. If run before /pentest:pentest, the orchestrator will respect the selection. If run standalone, does not launch a pentest.
pentest-kali
Connect to a Metasploit-Kali Server (MKS) REST API — verifies connectivity, discovers available Kali tools, and configures agents to prefer MKS endpoints over local Bash equivalents.
pentest-exit
Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.
bb-ad
Active Directory enumeration and attack techniques. Includes LDAP enumeration, Kerberos attacks (Kerberoasting, AS-REP Roasting), SMB attacks, and domain privilege escalation. Use this when targeting Windows domain environments.