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.
git clone --depth 1 https://github.com/atman-33/workhubWrote 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/plugins/atman-33/workhub/team-comms)<a href="https://agentmods.dev/plugins/atman-33/workhub/team-comms"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/team-comms/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/plugins/atman-33/workhub/team-comms"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/team-comms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
team-comms 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 11d 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
{
"name": "team-comms",
"version": "0.3.1",
"description": "Asynchronous discussion between each team member's coding agent over a shared folder (Google Drive, OneDrive, file server). Immutable append-only threads make write conflicts structurally impossible; research is shared as attachments instead of hand-delivered documents; notifications are opt-in per working directory, so a session that is not discussing anything stays silent.",
"author": {
"name": "atman-33",
"url": "https://github.com/atman-33"
}
}
What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 459 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 11d ago Changed 7bf2deabdad7
- 16d ago First seen · 10 lines scan A 95ef662f9536
team-comms is a plugin published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
lets
Development workflow with session management, code review, and task tracking.
sitrep-panel
A live local HTML report Claude keeps updated as it works — status board, running narrative, screenshots, newest-first log — so you can watch progress without reading the transcript.
csw
Ship a tracker ticket: dispatch it into a worktree, drive it to a pull request, merge it after review, and clean up after itself.
plan-cascade
AI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI…
delivery-loop
Agentic software-delivery loop: turn specs into a dependency-ordered GitHub Issues backlog, then let agents claim, implement, adversarially review, patch, and merge tasks in isolated git worktrees behind a single correctness gate.