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/steipete/agent-scripts/telecrawlnpx skills add steipete/agent-scripts --skill telecrawlgit clone --depth 1 https://github.com/steipete/agent-scriptsWhat 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.00023 | $0.00410 |
| Opus 5 | $0.00012 | $0.00205 |
| Sonnet 5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
telecrawl 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.
What it actually says
Telecrawl
Use this for Telegram history questions. Local archive first; the Telegram apps only for live/current state.
Sources
- DB:
~/.telecrawl/telecrawl.db - Import source: Telegram Desktop
tdataor native macOS Telegram Postbox (auto-detected) - CLI:
telecrawl - Archive host: the populated archive currently lives on
clawmac(~200 chats). Local DBs on other Macs may be empty — checkstatusfirst and prefer SSH to the archive host over answering from an empty DB:
ssh -o RequestTTY=no -o RemoteCommand=none steipete@clawmac 'zsh -lc "telecrawl --json status"'
Freshness
telecrawl --json status
Empty counts mean no import has run on this machine, not "no Telegram data".
Queries
All read commands take --json.
telecrawl --json chats --limit 20
telecrawl --json chats --unread
telecrawl --json messages --chat <ID> --limit 50 --after 2026-01-01
telecrawl --json search "query" [--chat ID]
telecrawl --json contacts --limit 50
telecrawl --json folders
telecrawl --json topics --chat <ID>
Import / Refresh
telecrawl doctor # verify a Telegram data source is readable
telecrawl import # merge-import from detected local Telegram app
telecrawl import --fetch-media # also pull Telegram cloud media
Imports merge by default; --restore replaces the archive — treat as destructive and confirm first.
Backup
Encrypted age shards to a git repo:
telecrawl backup status
telecrawl backup push
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 · 61 lines · 23 tokens per session scan A 4db095814333
telecrawl is a skill published in the GitHub repository steipete/agent-scripts (6,590 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 410 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…