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-review)<a href="https://agentmods.dev/commands/wshobson/agents/team-review"><img src="https://agentmods.dev/badge/commands/wshobson/agents/team-review/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-review"><img src="https://agentmods.dev/badge/commands/wshobson/agents/team-review.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.00012 | $0.00726 |
| Opus 5.5 | $0.00005 | $0.00290 |
| Sonnet 5.5 | $0.00002 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
team-review 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- team-review — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Review
Orchestrate a multi-reviewer parallel code review where each reviewer focuses on a specific quality dimension. Produces a consolidated, deduplicated report organized by severity.
Pre-flight Checks
- Verify
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1is set - Parse
$ARGUMENTS:<target>: file path, directory, git diff range (e.g.,main...HEAD), or PR number (e.g.,#123)--reviewers: comma-separated dimensions (default:security,performance,architecture)--base-branch: base branch for diff comparison (default:main)
Phase 1: Target Resolution
- Determine target type:
- File/Directory: Use as-is for review scope
- Git diff range: Use Bash to run
git diff {range} --name-onlyto get changed files - PR number: Use Bash to run
gh pr diff {number} --name-onlyto get changed files
- Collect the full diff content for distribution to reviewers
- Display review scope to user: "{N} files to review across {M} dimensions"
Phase 2: Team Spawn
- Use
TeamCreatetool to create the team withteam_name: "review-{timestamp}"anddescription - For each requested dimension, use
Agenttool to spawn a teammate:name:{dimension}-reviewer(e.g., "security-reviewer")subagent_type: "agent-teams:team-reviewer"prompt: Include the dimension assignment, target files, and diff content
- Use
TaskCreatefor each reviewer's task:- Subject: "Review {target} for {dimension} issues"
- Description: Include file list, diff content, and dimension-specific checklist
Phase 3: Monitor and Collect
- Wait for all review tasks to complete (check
TaskListperiodically) - As each reviewer completes, collect their structured findings
- Track progress: "{completed}/{total} reviews complete"
Phase 4: Consolidation
- Deduplicate: Merge findings that reference the same file:line location
- Resolve conflicts: If reviewers disagree on severity, use the higher rating
- Organize by severity: Group findings as Critical, High, Medium, Low
- Cross-reference: Note findings that appear in multiple dimensions
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 · 79 lines · 12 tokens per session scan A 4082b340224f
team-review is a command published in the GitHub repository wshobson/agents (41,247 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 726 once invoked, about $0.0000 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
qa-loop
Autonomous loop AUDIT (parallel) → VALIDATE → FIX → VERIFY → CHECK with stopping criteria.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
qa-review
Performs a thorough and constructive code review.
review-functional
Validate feature completeness, acceptance criteria, user experience, and functional requirements alignment with PRD/task specifications.
validate-parallel
Run assert and review-code commands in parallel to reduce validation time by 50%.
audit-cross-duplication
Detect N×M concern duplication across sibling directories and generate a prioritised refactoring narrative.