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 tomzx/agents --skill slack-kb-channelgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/slack-kb-channel)<a href="https://agentmods.dev/skills/tomzx/agents/slack-kb-channel"><img src="https://agentmods.dev/badge/skills/tomzx/agents/slack-kb-channel/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/tomzx/agents/slack-kb-channel"><img src="https://agentmods.dev/badge/skills/tomzx/agents/slack-kb-channel.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.00045 | $0.01221 |
| Opus 5 | $0.00023 | $0.00611 |
| Sonnet 5 | $0.00009 | $0.00244 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
slack-kb-channel 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack channel knowledge base
Use when building or updating a Slack channel knowledge base for a given month. Works for any channel you have access to; you need its Slack channel id (starts with C for public channels).
Memory (canonical — ship this)
Temporal memory (time-sliced, one file per calendar month) lives under memory/temporal/. That directory name signals content keyed by when it was observed, not by long-lived theme.
| Path | Purpose |
|---|---|
memory/temporal/<channel-slug>-YYYY-MM.md |
Channel themes, incidents, pointers, and thread-derived findings (thematic digest keyed by thread_ts; no exhaustive thread list in the file) |
Use a stable short slug for the channel in the filename (e.g. help-ml-infrastructure, team-foo-oncall), so the same channel always maps to the same prefix. You may include the channel id in prose or front matter if that helps disambiguation.
Do not add a separate -threads.md or other companion KB files for the same month.
Rules for memory
- Dates in prose: Prefer
YYYY/MM/DDfor a specific day andYYYY/MMfor a month (e.g. incident windows, “seen in” notes). Avoid English month names or abbreviations (Feb,March 2026) in running text unless quoting Slack verbatim. - Do not include a thread index (full table of every
thread_ts+ topic) in the monthly markdown. Use thread-derived findings only, withthread_tsinline where it helps. - Do not link to, name, or point readers at raw thread capture files (e.g. per-thread markdown exports, “dump” directories, or filenames derived from timestamps). Those are ingestion artifacts, not the KB.
- Thread identity in memory is
thread_ts(and channel id when the slug alone is ambiguous). People re-open discussions in Slack using those ids. - When merging new facts from Slack, update the single monthly file under
memory/temporal/only; do not add “see file X in folder Y” for raw captures.
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.
- 7d ago First seen · 69 lines · 45 tokens per session scan A f86726e49244
slack-kb-channel is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,221 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.