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 kellvembarbosa/team-orchestrator/plugin install teamWrote 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/commands/kellvembarbosa/team-orchestrator/product-manager)<a href="https://agentmods.dev/commands/kellvembarbosa/team-orchestrator/product-manager"><img src="https://agentmods.dev/badge/commands/kellvembarbosa/team-orchestrator/product-manager/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/commands/kellvembarbosa/team-orchestrator/product-manager"><img src="https://agentmods.dev/badge/commands/kellvembarbosa/team-orchestrator/product-manager.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.00006 | $0.00122 |
| Opus 5 | $0.00003 | $0.00061 |
| Sonnet 5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
product-manager 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 9d 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.
This is a copy
86% identical to accessibility-analyst — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Spawn an agent team named "product-manager" using the stored team definition.
- Read the team configuration from
${CLAUDE_PLUGIN_ROOT}/teams/product-manager.md. Frontmatter may includemodelandsizehints; body holds the team's instructions. - Create an agent team that follows those instructions. Honor
modelandsizehints if present. - Incorporate this additional user context into the spawn prompt (may be empty): $ARGUMENTS
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.
- 9d ago First seen · 12 lines · 6 tokens per session scan A f5ec41352607
product-manager is a command published in the GitHub repository kellvembarbosa/team-orchestrator (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 122 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to accessibility-analyst, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
linear-curator-run
Run the curator — collect signals from configured signal sources and report.
linear-sync
Populate or refresh the Linear reference files (teams, projects, users, workflows).