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 slackxgit 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/slackx)<a href="https://agentmods.dev/skills/tomzx/agents/slackx"><img src="https://agentmods.dev/badge/skills/tomzx/agents/slackx/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/slackx"><img src="https://agentmods.dev/badge/skills/tomzx/agents/slackx.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 54 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 56 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00145 | $0.04115 |
| Opus 5.5 | $0.00058 | $0.01646 |
| Sonnet 5.5 | $0.00029 | $0.00823 |
| Haiku 4.5 | $0.00015 | $0.00411 |
Grade A, and why
slackx 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 1mo 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slackx Skill
slackx is a small Python CLI (package name slack-cached) that caches Slack
threads, channel messages, DMs, users, and channels to a local SQLite database.
Given a Slack permalink (or a channel and root timestamp), it fetches the thread
via conversations.replies and stores every message. On subsequent runs it only
fetches new replies (and detects edits) by passing oldest to the API based on
the highest cached ts.
It is the single source of Slack thread content for the other Slack skills:
slack-resolve-threads reads threads through slackx conversations show, and
the knowledge-base skills use it to cache and render conversations.
Command tree
The CLI is grouped into subcommands. The old flat commands (fetch, show,
search, poll, fetch-users, fetch-channels, show-users,
show-channels, show-channel) no longer exist.
slackx
conversations fetch | show | search | poll
channels fetch | list
users fetch | list
cache status | clear
serve
Every command takes --help (or -h) and shows its own options and
positional arguments.
Options live on the leaf command
--db, --workspace, --api-base-url, and --log-level are options on each
leaf command, not on slackx itself. Put them after the command:
slackx cache status --db /tmp/x.db --log-level debug
slackx users list --json --workspace acme
The equivalent environment variables (for example SLACK_API_BASE_URL) still
apply process-wide and are the easiest way to point every command at an
alternate API. There is no top-level -v/--verbose; use --log-level
(debug, info, warning, error, critical, default info).
Prerequisites
Binary
Check whether the binary is on PATH; install from the source repo if not:
if ! command -v slackx &>/dev/null; then
git clone https://github.com/TomzxCode/slackx /tmp/slackx
uv tool install /tmp/slackx
fi
The install provides two binaries, slackx and slack-fake-server. If
uv tool install isn't desired, run it in place with
uv run --project /tmp/slackx slackx .... Confirm it works: slackx --help.
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.
- 1mo ago Changed · +88 lines · +3 tokens per session 3eabcc57c09c
- 1mo ago Changed · +24 lines 005bc85c0297
- 1mo ago Changed · +14 lines · -8 tokens per session f69efe44f644
- 1mo ago First seen · 322 lines · 150 tokens per session scan A 13f0f5b08d8f
slackx is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 145 tokens to every session and 4,115 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
Migrate
Intakes external content (notes, CLAUDE.md, Cursor rules, Obsidian/Notion/Apple Notes exports), classifies chunks against the LifeOS taxonomy, and commits with provenance after confidence-tiered approval. USE WHEN /migrate, migrate content, import from other LifeOS, bring in old notes, import Cursor rules, import…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
Profile
View, edit, or clear the LifeOS User Model (PRINCIPALIDENTITY.md) — persistent identity context loaded at session startup. Three intents: View, Edit (identity, goals, constraints, preferences), Clear (reset). Read by Algorithm OBSERVE and skills for personalization. USE WHEN profile, show profile, view profile, who am…
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
session-compact
AI DevKit · Compact a historical AI coding session with Jev when context is long, work is handed off or resumed, or durable continuation facts and memory candidates need extraction.