Agentic Plugin Marketplace is a collection of reusable plugins, agents, skills, commands, and rules for coding-agent tools including Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, and GitHub Copilot. It is for developers assembling agentic workflows across multiple harnesses from shared Markdown sources, and the catalogue entries are examples or subsets of those workflow components.
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/wshobson/agentsWrote 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/wshobson/agents/team-status)<a href="https://agentmods.dev/commands/wshobson/agents/team-status"><img src="https://agentmods.dev/badge/commands/wshobson/agents/team-status/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/wshobson/agents/team-status"><img src="https://agentmods.dev/badge/commands/wshobson/agents/team-status.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.00014 | $0.00448 |
| Opus 5.5 | $0.00006 | $0.00179 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
team-status 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 1mo 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
Team Status
Display the current state of an active agent team including members, tasks, and progress.
Phase 1: Team Discovery
-
Parse
$ARGUMENTSfor team name and flags:- If team name provided, use it directly
- If no team name, check
~/.claude/teams/for active teams - If multiple teams exist and no name specified, list all teams and ask user to choose
--tasks: show only task details--members: show only member details--json: output raw JSON instead of formatted table
-
Read team config from
~/.claude/teams/{team-name}/config.jsonusing the Read tool -
Call
TaskListto get current task state
Phase 2: Status Display
Members Table
Display each team member with their current state:
Team: {team-name}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Members:
Name Role Status
─────────────────────────────────────────
security-rev team-reviewer working on task #2
perf-rev team-reviewer idle
arch-rev team-reviewer working on task #4
Tasks Table
Display tasks with status, assignee, and dependencies:
Tasks:
ID Status Owner Subject
─────────────────────────────────────────────────
#1 completed security-rev Review auth module
#2 in_progress security-rev Review API endpoints
#3 completed perf-rev Profile database queries
#4 in_progress arch-rev Analyze module structure
#5 pending (unassigned) Consolidate findings
Progress: 40% (2/5 completed)
JSON Output
If --json flag is set, output the raw team config and task list as JSON.
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.
- 1mo ago First seen · 61 lines · 14 tokens per session scan A ac797ec168d3
team-status is a command published in the GitHub repository wshobson/agents (41,158 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 448 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
backlot
Open the Backlot living storyboard — the browser board that shows pipeline stages, script, scene plan, and generated assets live as a production runs.
resolve_todo_parallel
Resolve all pending CLI todos using parallel processing.
portfolio-status
Review the health of all projects in the portfolio.
signal-planner
Closed-loop autonomy — convert a production/analytics/incident signal into a dependency-ordered issue DAG, execute via /orchestrate, then verify the originating signal is resolved. Event-driven companion to /autopilot.
orchestrate
Orchestrate several issues in parallel — launches one lean work-on lane per issue (background shell or agent), GitHub is the register.
ops-standup
Morning briefing: commits, PRs, CI, blockers and priorities of the day.