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 skills add tigu77/tiguclaw --skill telegram-connectgit clone --depth 1 https://github.com/tigu77/tiguclawWrote 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/tigu77/tiguclaw/telegram-connect)<a href="https://agentmods.dev/skills/tigu77/tiguclaw/telegram-connect"><img src="https://agentmods.dev/badge/skills/tigu77/tiguclaw/telegram-connect/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/skills/tigu77/tiguclaw/telegram-connect"><img src="https://agentmods.dev/badge/skills/tigu77/tiguclaw/telegram-connect.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.00050 | $0.00648 |
| Opus 5.5 | $0.00020 | $0.00259 |
| Sonnet 5.5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
telegram-connect 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 today.
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
텔레그램 연결
연결은 대시보드 → 플러그인 → 텔레그램 채널(telegram-channel) 설정에서 한다. .env 를 직접 고치게 하거나 터미널 명령을
시키지 않는다 — 그 화면이 같은 파일에 안전하게 쓴다.
사용자에게 안내할 순서
- 봇 만들기 — 텔레그램에서 @BotFather 를 열고
/newbot을 보낸다. 이름과 아이디(…bot으로 끝남)를 정하면123456789:AA…모양의 토큰을 준다. - 토큰 넣기 — 대시보드 플러그인 화면의 텔레그램 «봇 토큰» 칸에 붙여넣는다(값은 다시 화면에 나오지 않는다).
- 재시작 — 화면 위 «지금 재시작» 을 누른다(또는 사용자가 원하면 비서가 재시작한다). 이제 봇이 메시지를 받는다(아직 잠긴 상태).
- 봇에게 말 걸기 — 텔레그램에서 방금 만든 봇을 찾아 아무 말이나 한 번 보낸다(아직 답은 없다 — 정상이다).
- 내 ID 찾기 — 같은 화면의 «소유자 ID» 옆 «내 ID 찾기» 를 누르고, 목록에서 자기 이름을 고른다. 고르는 즉시 통한다 (재시작 다시 필요 없음) — 봇에게 다시 말을 걸면 답한다.
지킬 것
- ★토큰을 채팅으로 받지 않는다. 붙여넣겠다고 하면 위 2번 칸으로 안내한다 — 채팅에 쓴 값은 대화 기록과 모델 요청에 남는다.
이미 채팅에 붙여넣었다면 그 사실을 알리고 BotFather 의
/revoke로 새 토큰을 받으라고 권한다. - 소유자 ID 는 사용자가 고른다 — 목록 맨 위를 알아서 넣지 않는다(봇 이름이 알려지면 남이 먼저 말을 걸 수 있다).
- 소유자 ID 가 비어 있으면 봇은 잠긴다(아무에게도 답하지 않는다). 연결이 안 된다면 먼저 이 칸을 확인한다.
- 한 토큰은 한 곳에서만 받을 수 있다 — 같은 토큰을 다른 기기·인스턴스에도 넣으면 서로 끊는다(로그에
409). - 연결 뒤 확인은 데몬 로그의
telegram:줄로 한다(allowlist 활성·차단된 접근· 폴링 오류).
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.
- today First seen · 29 lines · 50 tokens per session scan A 05d9a6c133ac
telegram-connect is a skill published in the GitHub repository tigu77/tiguclaw (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 648 once invoked, about $0.0002 per session on Opus 5.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-10-17.
Other skills, from other repositories
tmux
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).
community-research-insight
Extract structured insight briefs from community research transcripts or notes. Produces pain points, stakeholder needs, opportunity maps, risks, and follow-up questions. Requires human review before publication.
telegram-userbot
A skill for connecting to and working through the owner's personal Telegram account, rather than a Telegram bot. It can read personal chats, search messages, and send messages as the account owner after setup and consent.
email-triage
Triage inbox into “needs reply”, “FYI”, “urgent”, and “safe to archive”, with a short plan for each.
watch
A monitoring and briefing workflow that checks unread Telegram messages, email, failed checks, and failed scheduled units, then decides what needs the owner's attention. It can also explain actions such as creating a task, delaying a reminder, ignoring an item, or fixing a failure.
insight
A scheduled daily practice that looks for a repeated manual task, builds and tests a small tool for it, and suggests the result. It can instead report a development issue when the agent cannot solve its own problem.