team

team is a command for Claude Code from isaacsight/kernel. It costs 0 tokens per session (537 once invoked), scanned A, original, MIT.

A team command that runs six specialist reviews in sequence and combines their findings into one report.

In plain words
What is it for?
Use it to check current changes across security, testing, design, performance, DevOps, and product areas before release.
Why use it?
Later reviews can use earlier findings, giving you one coordinated assessment of security, quality, design, performance, operations, and product concerns.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to check current changes across security, testing, design, performance, DevOps, and product areas before release.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/isaacsight/kernel/team
Install

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.

Clone the repo
git clone --depth 1 https://github.com/isaacsight/kernel

Made for: Claude Code.

Wrote 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.

agentmods badge for team

README.md
[![agentmods](https://agentmods.dev/badge/commands/isaacsight/kernel/team/github.svg)](https://agentmods.dev/commands/isaacsight/kernel/team)
Your own site
<a href="https://agentmods.dev/commands/isaacsight/kernel/team"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/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.

agentmods 80×15 button for team

Your own site · 80×15
<a href="https://agentmods.dev/commands/isaacsight/kernel/team"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 537 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00537
Opus 5.5 $0.00000 $0.00215
Sonnet 5.5 $0.00000 $0.00107
Haiku 4.5 $0.00000 $0.00054

Measured 2mo ago against content hash 623c8825ada5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/team.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run all 6 agents against the current changes and synthesize a unified report.

This command runs each agent sequentially so findings can inform subsequent agents.

Execution Order

1. Security Agent

  1. Call agent_memory_read for security
  2. Run kernel_audit
  3. Scan for hardcoded secrets in src/ and tools/
  4. Verify edge function auth
  5. Call agent_memory_write for security

2. QA Agent

  1. Call agent_memory_read for qa
  2. Run npx tsc --noEmit
  3. Run npm run build
  4. Use Playwright to screenshot key screens
  5. Call agent_memory_write for qa

3. Designer Agent

  1. Call agent_memory_read for designer
  2. Run kernel_design_lint on changed files
  3. Audit typography, palette, touch targets, dark mode
  4. Call agent_memory_write for designer

4. Performance Agent

  1. Call agent_memory_read for performance
  2. Measure bundle sizes from build output
  3. Run kernel_deps and kernel_uptime
  4. Check against budgets
  5. Call agent_memory_write for performance

5. DevOps Agent

  1. Call agent_memory_read for devops
  2. Review build output and deployment readiness
  3. Check infrastructure health
  4. Call agent_memory_write for devops

6. Product Agent

  1. Call agent_memory_read for product
  2. Navigate live site with Playwright
  3. Evaluate discoverability, clarity, value delivery
  4. Score findings with ICE framework
  5. Call agent_memory_write for product

Synthesis

After all agents complete, call team_report to synthesize findings into a unified report with:

  • Blockers — Must fix before shipping
  • Warnings — Should fix soon
  • Suggestions — Nice to have
  • Cross-cutting themes — Patterns spanning multiple agents
  • Recommended next actions — Prioritized list

Also update shared-knowledge.md with any cross-cutting insights discovered.

Output

# Team Report — [date]

## Agent Results
| Agent | Status | Findings | Critical |
|-------|--------|----------|----------|

## Unified Assessment
[synthesized findings from team_report]

## Priority Actions
1. [highest priority]
2. ...

Read the full file on GitHub · 74 lines

Changes

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.

  1. 2mo ago First seen · 74 lines · 0 tokens per session scan A 623c8825ada5

Subscribe to this mod's changes

team is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 537 tokens. 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-09-03.

Related

team compared with commands from other repositories

team next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
teamisaacsight/kernelCommand161mo agoMITA0Claude Code
dart-fix-cidartsim/dartCommand1.2kyesterdayBSD-2-ClauseA6Claude Code
domainsgotempsh/tempsCommand903yesterdayApache-2.0A0Claude Code
riskreviewinclusionAI/AvernetCommand601yesterdayApache-2.0A11Claude Code
check-release-healthopenshift-eng/ai-helpersCommand122yesterdayApache-2.0A22Claude Code
anchorsraccioly/docguardCommand322d agoMITA11Claude Code
release-managerruvnet/agentic-flowCommand838yesterdaynoneA0Claude Code