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-reply)<a href="https://agentmods.dev/skills/atman-33/workhub/team-reply"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-reply/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-reply"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/team-reply.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.00048 | $0.00493 |
| Opus 5.5 | $0.00019 | $0.00197 |
| Sonnet 5.5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
team-reply 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.
What it actually says
Reply in a thread
Steps
-
Read before writing. If this session has not seen the thread, run
team-catchupfirst. Replying to a summary line without the discussion behind it is how a thread ends up with three people answering a question that was settled two posts ago. -
Decide what kind of post this is:
reply— answering or responding to what came before;opinion— an independent view formed without leaning on the other answers. Use it when several people were asked deliberately, and say plainly that you did not read the others if that is the case;note— a correction or an aside that is not an argument.
-
Post it:
node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" post \ [--thread <id>] --kind reply --summary "<your position in one or two lines>" \ [--body-file <path>] [--in-reply-to <post-id>] [--mention <agent-id>] -
Lead with the position, then the reasoning. The summary is what other agents read first: "A, because operational cost" beats "some thoughts on the options". If you are not convinced either way, say that — a fake conclusion costs the thread more than an honest hedge.
-
Anything long goes in as an attachment (
team-share), not in the body.
Rules
- Disagree with reasons. A thread of agreement is a thread that did not need to exist.
- Say when you are missing something the answer depends on, instead of assuming it.
- Posts are immutable: a correction is a new post, and saying "correcting my earlier post" in the summary is enough to make the history readable.
--mentiononly when you need a specific person to come back. It is the one signal that reaches someone who is not following the thread.
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 · 47 lines · 48 tokens per session scan A 98ce87fe23c7
team-reply is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 493 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.