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.
npx agentmods add commands/isaacsight/kernel/teamgit clone --depth 1 https://github.com/isaacsight/kernelWrote 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/isaacsight/kernel/team)<a href="https://agentmods.dev/commands/isaacsight/kernel/team"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/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 | $0.00000 | $0.00537 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 yesterday.
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.
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
- Call
agent_memory_readforsecurity - Run
kernel_audit - Scan for hardcoded secrets in
src/andtools/ - Verify edge function auth
- Call
agent_memory_writeforsecurity
2. QA Agent
- Call
agent_memory_readforqa - Run
npx tsc --noEmit - Run
npm run build - Use Playwright to screenshot key screens
- Call
agent_memory_writeforqa
3. Designer Agent
- Call
agent_memory_readfordesigner - Run
kernel_design_linton changed files - Audit typography, palette, touch targets, dark mode
- Call
agent_memory_writefordesigner
4. Performance Agent
- Call
agent_memory_readforperformance - Measure bundle sizes from build output
- Run
kernel_depsandkernel_uptime - Check against budgets
- Call
agent_memory_writeforperformance
5. DevOps Agent
- Call
agent_memory_readfordevops - Review build output and deployment readiness
- Check infrastructure health
- Call
agent_memory_writefordevops
6. Product Agent
- Call
agent_memory_readforproduct - Navigate live site with Playwright
- Evaluate discoverability, clarity, value delivery
- Score findings with ICE framework
- Call
agent_memory_writeforproduct
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. ...
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.
- yesterday First seen · 74 lines · 0 tokens per session scan A 623c8825ada5
team is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 6d 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.
Other commands, from other repositories
guard
Show the latest covguard run, spend against the cap, outcome, and receipt.
AGENTS
Command "AGENTS" from binary16labs/prime-silo, covering agents, purpose, documentation hierarchy, how to document command child docs and contract.
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
adr
You are helping create a new ADR (Architecture Decision Record). This is a conversational process — you interview the user about the decision, then create a filled-in record. ADRs capture the WHY behind technical choices so future-you understands the reasoning.