find-discussions

find-discussions is a command for Claude Code from anthropics/knowledge-work-plugins. It costs 9 tokens per session (205 once invoked), scanned A, original, Apache-2.0.

A Slack search command that finds discussions about a topic, reads the relevant conversation threads, and summarises the most useful results.

In plain words
What is it for?
It helps locate decisions, conclusions, unresolved questions, and related conversations in Slack.
Why use it?
It saves time when information is spread across channels and the surrounding thread contains important context.

Command for Claude Code ✓ vendor

Written for Claude Code: $ARGUMENTS substitution.

Part of the slack-by-salesforce plugin — 2 skills, 5 commands shipped together

Good fit It helps locate decisions, conclusions, unresolved questions, and related conversations in Slack.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/anthropics/knowledge-work-plugins/find-discussions
About the project

Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.

anthropics/knowledge-work-plugins · 23,911 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/anthropics/knowledge-work-plugins

Made for: Claude Code.

Or install slack-by-salesforce, the plugin that ships this one along with the rest of its 2 skills, 5 commands.

Wrote 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.

agentmods badge for find-discussions

README.md
[![agentmods](https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/find-discussions.svg)](https://agentmods.dev/commands/anthropics/knowledge-work-plugins/find-discussions)
Your own site
<a href="https://agentmods.dev/commands/anthropics/knowledge-work-plugins/find-discussions"><img src="https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/find-discussions.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 205 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00205
Opus 5 $0.00005 $0.00102
Sonnet 5 $0.00002 $0.00041
Haiku 4.5 $0.00001 $0.00020

Measured 4d ago against content hash 42e140bb8048, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

partner-built/slack/commands/find-discussions.md · 16 lines

What it actually says

Given the topic provided in $ARGUMENTS:

  1. Use the slack_search_public tool to search for messages matching the topic. Use the topic as a natural language question first for semantic results.
  2. If semantic results are sparse, follow up with a keyword search using key terms from the topic.
  3. For the most relevant results, use slack_read_thread to fetch full thread conversations so you capture the complete discussion context.
  4. 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.
  5. Limit output to the top 5-10 most relevant discussions to keep results manageable.
  6. If no results are found, suggest alternative search terms or broader queries the user could try.
Changes

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.

  1. 4d ago First seen · 16 lines · 9 tokens per session scan A 42e140bb8048

Subscribe to this mod's changes

find-discussions is a command published in the GitHub repository anthropics/knowledge-work-plugins (23,911 stars, last pushed 2d ago), licensed Apache-2.0. 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-09-03.