team

A full coding workflow assigns different stages to named agents: project exploration, planning, implementation, cleanup, and review. It does not run automated tests.

In plain words
What is it for?
Use it for larger coding tasks that benefit from exploration, a written plan, implementation, cleanup, and code review.
Why use it?
It organizes a complete change across specialized stages while making the lack of automated testing explicit.

Command

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.

agentmods
npx agentmods add commands/dentiny/kon/team
Clone the repo
git clone --depth 1 https://github.com/dentiny/kon
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00029 $0.00137
Opus 5 $0.00015 $0.00068
Sonnet 5 $0.00006 $0.00027
Haiku 4.5 $0.00003 $0.00014

Measured yesterday against content hash e1ed8ac74720, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

adapters/claude-code/commands/team.md · 17 lines

What it actually says

User invoked /kon:team with arguments: $ARGUMENTS

Resolve once:

export KON_ROOT="$(python3 "$HOME/.kon/lib/_kon_paths.py" root)"

Follow $KON_ROOT/adapters/claude-code/ORCHESTRATION.md for command /kon:team. Read $KON_ROOT/commands/team.md and run the full orchestration flow. Do not answer directly.

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. yesterday First seen · 17 lines · 29 tokens per session scan A e1ed8ac74720

Subscribe to this mod's changes

team is a command published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 137 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-31.