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/howdeploy/kisa-stack/telegram-chat-wikinpx skills add howdeploy/kisa-stack --skill telegram-chat-wikigit clone --depth 1 https://github.com/howdeploy/kisa-stackWhat 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.00070 | $0.02696 |
| Opus 5 | $0.00035 | $0.01348 |
| Sonnet 5 | $0.00014 | $0.00539 |
| Haiku 4.5 | $0.00007 | $0.00270 |
Grade A, and why
telegram-chat-wiki 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telegram Chat Wiki
Overview
Этот скилл превращает Telegram-диалог из одноразовой переписки в долговременную wiki-память. Он нужен не для того, чтобы просто сохранить лог, а чтобы построить двухслойную память:
- сырой слой — разбитая по датам переписка;
- смысловой слой — страница собеседника с темами, проектами, договоренностями, промптами, практиками, советами, контактами и фактами.
Идея простая: пользователь кидает архив с перепиской, агент раскладывает ее в wiki, а потом может отвечать на вопросы по формуле вроде: «что я обсуждал с Колей?», «какие советы мне давал Ваня?», «какие проекты всплывали в чате с N?».
Это не заменяет встроенную память агента. Это отдельный, reviewable, Obsidian-friendly knowledge layer для конкретных диалогов.
When to Use
Используй этот скилл, когда пользователь:
- присылает архив/экспорт Telegram-переписки;
- хочет хранить переписки в LLM Wiki / Obsidian;
- просит разбить чат по дням или темам;
- спрашивает, что обсуждал с конкретным человеком;
- хочет извлечь из разговоров проекты, промпты, советы, контакты, практики и факты;
- хочет превратить messy chat history в рабочую knowledge base.
Не используй как основной режим, если:
- нужен просто разовый summary одного короткого фрагмента;
- пользователь не хочет ничего сохранять;
- переписка слишком чувствительная и он не подтверждал ее запись в wiki.
Canonical Storage Model
Предпочтительная структура в wiki:
wiki/
├── dialogues/
│ ├── kolya.md # hub-страница собеседника
│ └── marina.md
├── raw/
│ └── dialogues/
│ ├── kolya/
│ │ ├── 2026-05-21.md # сырой day-chunk
│ │ ├── 2026-05-22.md
│ │ └── ...
│ └── marina/
└── queries/
└── kolya-projects-2026-05-27.md # опциональные сохраненные синтезы
Layer split
raw/dialogues/<slug>/YYYY-MM-DD.md
- почти сырой лог;
- immutable-ish источник;
- сообщения одной календарной даты;
- нужен для проверки и доказуемости.
What ships with it
4 files 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 · 236 lines · 70 tokens per session scan A 2d4e1e48a57a
telegram-chat-wiki is a skill published in the GitHub repository howdeploy/kisa-stack (23 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 2,696 once invoked, about $0.0003 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…