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-ops)<a href="https://agentmods.dev/plugins/atman-33/workhub/team-ops"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/team-ops/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-ops"><img src="https://agentmods.dev/badge/plugins/atman-33/workhub/team-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
team-ops 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 22d 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-ops",
"version": "0.1.2",
"description": "Team operations on a shared folder as the single source of truth: team knowledge base, file-based product backlog, sprint ceremonies, multi-repo progress tracking, and daily burndown/spec reporting.",
"author": {
"name": "atman-33",
"url": "https://github.com/atman-33"
}
}
What it installs
The manifest is a name and a version. 13 skills travel with it, and installing the plugin installs all of them — 700 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill manage-backlog A 57 tokens
- Skill report-daily-progress A 62 tokens
- Skill setup-team-context A 67 tokens
- Skill load-project-context A 55 tokens
- Skill plan-sprint A 50 tokens
- Skill update-spec A 56 tokens
- Skill team-kb-save A 55 tokens
- Skill team-onboard A 55 tokens
- Skill review-sprint A 43 tokens
- Skill start-pbi A 55 tokens
- Skill team-kb-index A 54 tokens
- Skill team-kb-query A 45 tokens
- Skill write-retro A 46 tokens
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.
- 22d ago Changed 9b058e8f4e77
- 1mo ago Changed 538322ff741b
- 1mo ago First seen · 10 lines scan A cb069df00c97
team-ops is a plugin published in the GitHub repository atman-33/workhub (3 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-03.
Other plugins, from other repositories
corpus-pm
Pack orienté gestion de produit pour corpus : types d'entités PM, angles de revue et transferts beads adaptés aux équipes produit francophones.
loopcraft
Loop engineering for Claude Code — rubric+verifier self-correction, 5-stage memory protocol (fail→investigate→verify→distill→consult), autonomous backlog runner with pluggable sources (file/GitHub/Jira) and write-back.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
radin
Cost-optimized agentic workflow stack for solo devs: backlog orchestration (radin-batch, radin-plan, radin-review) plus curated companion tools.
vp-beads
Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory.
product-manager
A product-management copilot based on the Pragmatic Institute Framework (Foundations, Focus, Build). Guides PMs from a raw idea through market research, positioning, strategy, requirements, roadmap and launch — and produces a client-ready artifact (Markdown or Word .docx) at every stage.