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/ipythoning/b2b-sdr-agent-template/telegram-toolkitnpx skills add iPythoning/b2b-sdr-agent-template --skill telegram-toolkitgit clone --depth 1 https://github.com/iPythoning/b2b-sdr-agent-templateWhat 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.00000 | $0.01631 |
| Opus 5 | $0.00000 | $0.00816 |
| Sonnet 5 | $0.00000 | $0.00326 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
telegram-toolkit 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
telegram-toolkit — Telegram SDR Best Practices & Templates
Bot commands, inline keyboards, large file handling, and channel-specific sales strategies for Telegram-based B2B SDR.
Why Telegram for B2B Sales
| Advantage | Impact |
|---|---|
| No 72h window | Proactive outreach anytime — nurture, follow-ups, stalled leads |
| 2GB file limit | Full product catalogs, certifications, video demos |
| Bot commands | Structured self-service (/catalog, /quote, /status) |
| Inline keyboards | One-tap BANT qualification, 3-5x faster than free-text |
| Username-based | Lower barrier — customer doesn't expose phone number |
| Free API | No per-message cost |
| No account bans | Bot API is stable, unlike WhatsApp's aggressive anti-automation |
Bot Commands
Register these commands with @BotFather using /setcommands:
start - Welcome message and product overview
catalog - Browse product catalog
quote - Request a quotation
status - Check order or quote status
contact - Speak with a human representative
language - Change conversation language
Command Behavior
/start
- Detect language from Telegram user profile
- Send welcome message with company intro (2-3 sentences max)
- Create CRM record: source =
telegram_organic, status =new - Offer product categories via inline keyboard
- Begin BANT qualification naturally
/catalog
- Check CRM for customer's product interest (if returning)
- If known interest: Send relevant product section + full catalog link
- If unknown: Send inline keyboard with product categories
- Always include: specs, MOQ, typical lead time
- File format: PDF preferred, under 20MB per file
/quote
- Check if BANT data exists in memory
- If incomplete: Trigger inline keyboard qualification flow
- If complete: Generate quote draft → send to owner for approval
- Confirm to customer: "I'm preparing your quotation, will have it ready shortly."
/status
- Read CRM for customer's active records
- Return: latest status, pending actions, next follow-up date
- If quote_sent: "Your quote was sent on [date]. Would you like to discuss it?"
- If no records: "I don't have an active order for you yet. Would you like to start one?"
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 · 186 lines · 0 tokens per session scan A d709830be77b
telegram-toolkit is a skill published in the GitHub repository iPythoning/b2b-sdr-agent-template (170 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,631 tokens. 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
forward-deployed-selling
Operating doctrine for AI-era enterprise sales. Use when an agent works on accounts, deals, outreach, coaching, or pipeline — any revenue-affecting decision.
event-outbound
Create validated, buyer-first email and LinkedIn outreach sequences for B2B conferences and trade shows, from pre-event through post-event. Use when asked to build attendee outreach, cold emails, LinkedIn cadences, side-event or dinner invitations, booth follow-up, or an event-plus-ICP campaign intended to book…
cold-email-onboarding
First-run interactive setup for the cold-email skill pack. Walks the operator through brand-config.json (ICP, PSP, EVP, tone, infrastructure) and SOUL.md (voice fingerprints, banned phrases, stories you lean on) in 10 minutes. Refuses to let the operator skip — generic output is worse than no output. Loaded…
cold-email-kickoff
Adaptive router for the cold-email skill pack. Detects the operator's current state (brand-config present? SOUL.md present? infrastructure ready? PSP defined? EVP locked? first campaign run?) and picks the next-best step. Loaded by the main cold-email skill on bare invocation ("/cold-email") or when the operator asks…
cold-email-list-quality
Score a cold-email prospect list 0-100 across dedup, role-fit (vs brand-config.icp), signal freshness, email-validity heuristics, exclusion-criteria match, and company-stage match. Returns the score, list of rows to remove, and a fix recommendation. Loaded by cold-email-weekly-rhythm on Monday's list refresh. Operates…
cold-email-reply-scoring
Classify replies to cold email into 4 categories — buy-signal, positive, neutral, not-interested — using deterministic features (intent keywords, time-to-reply, length, question count, calendar/asset asks). Routes each reply per brand-config.operations.replyrouting. Backed by a Python script that uses regex + features…