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/berkcangumusisik/agent-hubWrote 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/berkcangumusisik/agent-hub/team)<a href="https://agentmods.dev/commands/berkcangumusisik/agent-hub/team"><img src="https://agentmods.dev/badge/commands/berkcangumusisik/agent-hub/team.svg" alt="Measured on agentmods" 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.00022 | $0.00145 |
| Opus 5 | $0.00011 | $0.00072 |
| Sonnet 5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
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 8d 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
Report on the super-team for this project.
- Use the load-profile skill to read
.claude/agent-hub/profile.yml. - List the full roster (tech-lead, architect, backend-engineer, frontend-engineer, mobile-engineer, devops-engineer, code-reviewer, qa-tester, security-reviewer, tech-writer) with a one-line description each.
- Mark which ones are in this project's
team.active. - If there's no profile yet, tell me to run
/onboardfirst.
$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.
- 8d ago First seen · 13 lines · 22 tokens per session scan A f0f275207c84
team is a command published in the GitHub repository berkcangumusisik/agent-hub (14 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 145 once invoked, about $0.0001 per session on Opus 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
epic-claim
Claim an epic issue, stamp coordination state, and sync local ownership.
epic-decompose
Break an epic into task children without creating task branches.
epic-review
Mark epic review requested, approved, or changes requested.
epic-unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.