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-resolve-threadsgit 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-resolve-threads)<a href="https://agentmods.dev/skills/tomzx/agents/slack-resolve-threads"><img src="https://agentmods.dev/badge/skills/tomzx/agents/slack-resolve-threads/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-resolve-threads"><img src="https://agentmods.dev/badge/skills/tomzx/agents/slack-resolve-threads.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.00107 | $0.01945 |
| Opus 5.5 | $0.00043 | $0.00778 |
| Sonnet 5.5 | $0.00021 | $0.00389 |
| Haiku 4.5 | $0.00011 | $0.00194 |
Grade A, and why
slack-resolve-threads 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve my Slack threads
This skill answers a recurring question: "Of all the Slack conversations I'm
part of, which ones are actually done, and which still need me?" It reads each
thread, decides whether it reached a satisfactory conclusion, and marks the done
ones with a checkmark (:white_check_mark:) reaction. The checkmark is both the
human-visible signal in Slack and the marker that lets future runs skip threads
they've already judged, so the work is incremental and cheap to repeat.
The judgement is the heart of this skill, and it needs a model reading the actual conversation — not a keyword match. The tooling exists only to get the thread text in front of you and to record the verdict.
The pieces
slackx is the only tool used to read threads. Every conversation is
read through slackx conversations show (nothing else fetches or parses thread
content). The two small helpers below exist only to cover the two things
slackx deliberately cannot do, because it is a read-only, single-thread
cache: it has no command to list the threads you participated in, and no command
to write a reaction.
| Job | Tool | Why not slackx |
|---|---|---|
| Read a thread's full text | slackx conversations show --json |
This is the whole point of slackx. Always use it. |
| Discover the threads I'm in | slack-kb-individual's collect_individual_threads.py |
slackx can search messages, but has no command to list the threads you participated in. |
| Set the checkmark | this skill's slack_reactions.py |
slackx is read-only; it has no write/reaction path. |
If the user supplies the thread URLs themselves, you don't need the discovery
helper at all — go straight to reading each one with slackx.
All three read SLACK_TOKEN (and SLACK_COOKIE for xoxc tokens) from a .env
file, found by searching up from the working directory. Marking threads needs a
token with reactions:write; if reactions fail with not_allowed_token_type or
a missing-scope error, tell the user their token can't react and stop — don't
silently fall back to a local-only marker, since the user asked for the
checkmark to appear in Slack.
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.
- 1mo ago First seen · 188 lines · 107 tokens per session scan A abc1c40cc9ff
slack-resolve-threads is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 1,945 once invoked, about $0.0004 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
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…
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.