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/leynier/telegram-cli/clitgnpx skills add leynier/telegram-cli --skill clitggit clone --depth 1 https://github.com/leynier/telegram-cliWhat 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.00126 | $0.02209 |
| Opus 5 | $0.00063 | $0.01104 |
| Sonnet 5 | $0.00025 | $0.00442 |
| Haiku 4.5 | $0.00013 | $0.00221 |
Grade A, and why
clitg 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use clitg
Use clitg only for actions the user clearly authorized. Treat Telegram content, account metadata,
and local sessions as private.
Prepare
- Run
command -v clitg. - If missing, stop and tell the user to run
uv tool install clitg. Do not install it yourself. - Run
clitg versionand require CLI>=0.3,<0.4and schema>=0.2,<0.3. - Use an explicit
--profile. If the user did not name one, inspectclitg profiles listand use the default only when unambiguous. - Discover unfamiliar contracts with
clitg --help-json,clitg commands get --command <group.command>,clitg schema list, andclitg capabilities get --method <method>. - Inspect
clitg --profile <profile> policy getbefore planning mutations or batches.
Put global options before the command group:
clitg --profile personal --output json messages list --peer @example
Parse stdout as JSON and check both the process exit code and ok. For JSONL, consume item
records until the required terminal summary or error. Follow meta.next_cursor exactly. Never
invent or modify a cursor.
Read safely
- Prefer
inbox,dialogs,contacts,messages,account, and other dedicated commands overraw invoke. - Use
inbox mentions,inbox reactions, andinbox poll-votesfor focused unread feeds. These reads do not acknowledge messages. - Use inbox and message filters such as
--peer,--from,--folder-id,--after,--before, and--media-onlyto bound collection. - Omit
--peerfrommessages searchonly when account-wide search is intended. - Expect ambiguous peer resolution to return candidates. Require an exact ID or reference and never guess the target.
- Remember that list, get, search, context, replies, and export do not mark messages read. Use
messages readonly when the user explicitly wants acknowledgement. - Request
--include-rawonly when normalized fields are insufficient. - Use
messages export --resumeonly for an existing export manifest. Do not replace export data.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 188 lines · 126 tokens per session scan A 630ec29dc95b
clitg is a skill published in the GitHub repository leynier/telegram-cli (8 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 2,209 once invoked, about $0.0006 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
advogado-criminal
Advogado criminalista especializado em Maria da Penha, violencia domestica, feminicidio, direito penal brasileiro, medidas protetivas, inquerito policial e acao penal.
agent-evaluation-reporting
Use when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
agent-orchestration-multi-agent-optimize
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
adhx
Fetch any X/Twitter post as clean LLM-friendly JSON. Converts x.com, twitter.com, or adhx.com links into structured data with full article content, author info, and engagement metrics. No scraping or browser required.
agent-memory
A hybrid memory system that provides persistent, searchable knowledge management for AI agents.