What is team-threads?

A team-communication tool that lists live discussion threads, their state, unread posts, and who wrote last. It can also search threads and create a local browsable HTML list.

It helps catch up on unread posts, find discussions that mention you, choose a thread to join, and search team conversations.

It removes the need to open team discussions one by one to find what is unread or relevant. It helps distinguish discussions that need attention from those unrelated to today's work.

team-threads — Skill for Claude Code by atman-33/workhub

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add atman-33/workhub

Claude Code

/plugin install team-comms

Made for: Claude Code.

Or install team-comms, the plugin that ships this one along with the rest of its 8 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/atman-33/workhub/team-threads/github.svg)](https://agentmods.dev/skills/atman-33/workhub/team-threads)

Your own site

<a href="https://agentmods.dev/skills/atman-33/workhub/team-threads"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/atman-33/workhub/team-threads"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-threads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 453 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.

Model	Per session	Once invoked
Fable 5.1	$0.00059	$0.00453
Opus 5.5	$0.00024	$0.00181
Sonnet 5.5	$0.00012	$0.00091
Haiku 4.5	$0.00006	$0.00045

Measured 16d ago against content hash cea4bfab413f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-29, from the pricing page.

Security

Grade A, and why

team-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 16d 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.

plugins/team-comms/skills/team-threads/SKILL.md · 49 lines

What it actually says

See the team's threads

Steps

List them:
```
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" list
```
Add --all to include closed threads. scan additionally reports mentions and any stray files.
Report in the order that matters, not the order they came back: threads with unread posts first, then anything you are named in, then the rest. Give each one line: title, state, unread count, who wrote last.
Say what is worth doing, with a reason. Usually one of:
- read a thread that has unread posts (team-catchup);
- join the discussion the user is actually working on (team-focus);
- nothing, because none of it touches today's work — say that plainly rather than manufacturing a next step.
For a browsable copy, generate the local HTML list:
```
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" index
```
It is written under ~/.team-comms/, and deliberately not into the shared folder: one index file everyone rewrites is exactly the write conflict the rest of the design removes. Tell the user the path.
To find something specific, search rather than opening threads one by one: comms search "<text>".

Rules

scan reporting a conflict copy or a stray file is not noise. It means something wrote to the space without following the naming rules. Surface it, and leave the file where it is — moving someone's file is the user's call.
Do not open every thread to summarise the space. The summaries in list are there so nobody has to.

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.

16d ago First seen · 49 lines · 59 tokens per session scan A cea4bfab413f

Subscribe to this mod's changes

team-threads is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 453 once invoked, about $0.0002 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-13.

Claude Code Productivity Project management claude-code-plugin cross-platform desktop-app developer-tools obsidian

gonavi-cli

Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…

Syngnat/GoNavi · 144 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

protocol-tracker

Internal skill for commands. The tracker verb-resolution protocol - how a lets-tracker block resolves through the active adapter, the neutral read shape, body crossing, degradation, preflight and trust. Loaded by a command or skill right before its first tracker verb. Do not trigger on user conversation.

restarter/lets-workflow · 62 tokens

task-copilot

Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.

Everyone-Needs-A-Copilot/claude-copilot · 40 tokens

automation-architect

Workflow automation design using Zapier, Make, and n8n covering trigger-action architecture, multi-step automation workflows, error handling strategies, personal versus business automation patterns, ROI calculation, and a library of common automation recipes. Use when the user asks about automation architect, related…

FerroxLabs/wayland · 90 tokens

router

When unsure which TeamWorkflow skill applies, or orienting a new task or repository, find the right planning, research, building, review, or recovery workflow. Reuse recorded project bindings and working mode.

timharris707/skills · 43 tokens