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/Tenon-Net/Agent-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/plugins/tenon-net/agent-team/agent-team)<a href="https://agentmods.dev/plugins/tenon-net/agent-team/agent-team"><img src="https://agentmods.dev/badge/plugins/tenon-net/agent-team/agent-team/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/tenon-net/agent-team/agent-team"><img src="https://agentmods.dev/badge/plugins/tenon-net/agent-team/agent-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-team 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
{
"name": "agent-team",
"description": "Claude Code plugin: Claude orchestrates, Executor (grok or codex) implements tasks in isolated git worktrees, codex reviews read-only, Claude judges/reworks/merges. Review is never bypassed — including Claude's own fallback code.",
"version": "1.1.1",
"author": {
"name": "Tenon-Net"
},
"repository": "https://github.com/Tenon-Net/Agent-Team.git",
"homepage": "https://github.com/Tenon-Net/Agent-Team",
"license": "MIT",
"keywords": [
"claude-code",
"plugin",
"multi-agent",
"orchestration",
"grok",
"codex",
"code-review",
"worktree",
"ai-agents",
"agent-team"
]
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands travel with it, and installing the plugin installs all of them — 78 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 24 lines scan A f270eb518512
agent-team is a plugin published in the GitHub repository Tenon-Net/Agent-Team (2 stars, last pushed 2mo 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-08-31.
Other plugins, from other repositories
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
digest
Summarize AI-generated branches, PRs, and diffs into icon-rich cards, explain code state with git archaeology as self-contained HTML explainers, plus multi-project weekly recall digests.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
grok
Use Grok Build from Claude Code to review code or delegate tasks.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.