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.
/plugin marketplace add atman-33/workhub/plugin install team-commsWrote 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/atman-33/workhub/team-catchup)<a href="https://agentmods.dev/skills/atman-33/workhub/team-catchup"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-catchup/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/atman-33/workhub/team-catchup"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-catchup.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.00060 | $0.00616 |
| Opus 5.5 | $0.00024 | $0.00246 |
| Sonnet 5.5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
team-catchup 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Catch up on a thread
A session knows nothing about a thread it was not part of. Focus points at a thread; it does not remember its contents. This skill fills that gap — and it is the only part of team-comms that spends a meaningful number of tokens, so it reads incrementally and only when asked.
Steps
-
Pull what this session is missing:
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" catchup [<thread-id>]Defaults to the focused thread. It prints the cached digest first, then only the posts that arrived after it. With no digest yet, it prints the whole thread and says so.
-
Read summaries first. Open a post in full (
--full) or an attachment only where the summary is not enough to act on. Reading everything defeats the design — the summaries exist so you do not have to. -
Brief the user in a few lines: where the discussion stands, what is unresolved, who is waiting on what, and whether a decision has been recorded. If the tool reports more than one decision, say so — sync delay means two people can each believe theirs was the last word, and picking by timestamp would hide that. A person decides which stands.
-
Save an updated digest so the next session is cheap:
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" digest [<thread-id>] --file <path>Write 5–15 lines: the question, the positions and who holds them, what has been settled, what is open. Write it for a session that has never seen the thread — that is exactly who will read it.
-
If the thread is long and the user is joining cold,
--allre-reads everything from the start, ignoring the digest. Use it when the digest was written for a different purpose, not routinely.
Rules
- Never run this automatically at session start. Whether the discussion is worth loading is a judgement for the moment, which is why the hook injects summaries and stops there.
- The digest is your reading of the thread, cached on this machine. It is never written into the shared space — it is not a fact about the thread, and it would become one more file several people want to rewrite.
- Do not treat the digest as the source of truth when it matters: the posts are.
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 · 58 lines · 60 tokens per session scan A e3ddcff2178b
team-catchup is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 616 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.
Other skills, from other repositories
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…
to-tickets
When asked to file tickets, break down approved work, or move a settled plan onto the board, turn the spec, closed decision map, or pressure-tested conversation into verifiable work items with real dependencies and non-ticket blockers.
setup
For a new TeamWorkflow installation, binding refresh, or drift audit after a pack release, inspect and bind the project workflow. Reuse explicit recorded decisions with their sources; ask about missing, conflicting, or changed authority and bindings.
create-task
Create one production-ready task contract from a short request or optional structured brief, optional task ID, repository context, and attached references without implementing it. In the canonical task-first workflow this contract is also the implementable story; use separate story files only in an explicitly legacy…
decision-map
When asked to chart a decision map, work a map ticket, or plan work whose open decisions gate each other, map the unresolved choices before build slices. Use for a new primitive, milestone charter, or integration that cannot yet be specified in one sitting.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.