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 commands/slackapi/slack-skills-plugin/find-discussionsgit clone --depth 1 https://github.com/slackapi/slack-skills-pluginWhat 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.00009 | $0.00205 |
| Opus 5 | $0.00005 | $0.00102 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
find-discussions 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 3d 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
Given the topic provided in $ARGUMENTS:
- Use the
slack_search_publictool to search for messages matching the topic. Use the topic as a natural language question first for semantic results. - If semantic results are sparse, follow up with a keyword search using key terms from the topic.
- For the most relevant results, use
slack_read_threadto fetch full thread conversations so you capture the complete discussion context. - Present the results organized by relevance:
- For each discussion found, show: the channel name, who started it, a brief summary of the conversation, and the date.
- Group related discussions together if they span multiple channels.
- Highlight any conclusions, decisions, or unresolved questions.
- Limit output to the top 5-10 most relevant discussions to keep results manageable.
- If no results are found, suggest alternative search terms or broader queries the user could try.
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.
- 3d ago First seen · 16 lines · 9 tokens per session scan A 42e140bb8048
find-discussions is a command published in the GitHub repository slackapi/slack-skills-plugin (113 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 205 once invoked, about $0.0000 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 commands, from other repositories
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
webperf
Run a web performance audit via the web-performance-auditor persona.
spec
Start spec-driven development — write a structured specification before writing code.
audit-rules
Browse, enable, disable, and customize audit rules.
init
First-time setup. Auto-detects installed AI CLIs and configures targets.
search
Discover and install skills from GitHub repositories.