keel-agent-team-create

keel-agent-team-create is a skill for Claude Code from muratsilahtaroglu/claude-code-starter-kit. It costs 69 tokens per session (2,940 once invoked), scanned A, original, MIT.

An owner-only setup wizard for creating a team of coding agents that work in the same repository. It creates role descriptions, task lanes, and report folders for the team.

In plain words
What is it for?
Use it to create an orchestrator and specialist agents, assign their responsibilities, and prepare shared task and reporting files.
Why use it?
It gives same-machine agent sessions a defined roster and shared structure instead of leaving coordination informal. Ownership checks help control who can create or change the team setup.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions subagents.

Good fit Use it to create an orchestrator and specialist agents, assign their responsibilities, and prepare shared task and reporting files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create
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.

Any agent
npx skills add muratsilahtaroglu/claude-code-starter-kit --skill keel-agent-team-create
Clone the repo
git clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kit

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 keel-agent-team-create

README.md
[![agentmods](https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create/github.svg)](https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create)
Your own site
<a href="https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create"><img src="https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create/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 keel-agent-team-create

Your own site · 80×15
<a href="https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create"><img src="https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-agent-team-create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,940 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.00069 $0.02940
Opus 5.5 $0.00028 $0.01176
Sonnet 5.5 $0.00014 $0.00588
Haiku 4.5 $0.00007 $0.00294

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

Security

Grade A, and why

keel-agent-team-create 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.

.claude/skills/keel-agent-team-create/SKILL.md · 142 lines

How it starts

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

/keel-agent-team-create — build the agent team (owner-only)

When: the owner wants parallel Claude sessions in THIS repo to work like a specialized team (orchestrator · mechanic · frontend · test · provider…) instead of ad-hoc co-agents. This wizard CREATES the structure once; each chat later adopts an identity via /keel-agent-team-start @<name>. (Real human teams on different machines are /keel-team's job, not this one — the two can coexist: human lanes and agent lanes share the same TASKS board, and creation authority is the owner's in both.)

0. Owner gate (hard — creation is governance)

  • .claude/project-owner exists and git config user.name ≠ its content → STOP: "agent-team creation is owner-only — ask @". (The owner-guard hook independently blocks non-owner writes to .claude/agents/*; this check just fails politely and earlier.)
  • .claude/project-owner missing → offer to write it FIRST (arming owner-guard): a team without a declared owner has no enforceable governance. Only proceed after it exists.

1. Interview the owner (ask, don't assume)

  1. How many agents, and their names — single English tokens preferred (orchestrator, mechanic, frontend, test, provider…); the owner's naming always wins. Exactly ONE agent carries the orchestrator role.
  2. A task-id prefix per lane — derived from the names, confirmed by the owner: co-agent → co, frontend → fro, provider → prv; the orchestrator gets none (it takes no work items). That lane's items then run co1 · co2 · co3 …, allocated by the orchestrator alone so two sessions can't mint the same number. 2–4 lowercase letters, unique across BOTH the agent and the human roster, never reused, never renamed — the id also names reports/team/<name>/co3_*, <id>_spec.md and scratch/co3/, so renaming dangles permanent artifacts (§9.32, §10.40). One case only: a series split across r1 and R28 makes every count wrong (field case).
  3. Each worker's domain — mission (one line), scope paths (globs), anything it must NEVER touch.
  4. Charter/prompt language — EN or TR (the project's docs language usually decides). Note the invariant either way: machine-memory writes (boards, HANDOVER/LESSONS input) are ENGLISH (§9.31).
  5. Review routing notes — the default is review-v2 (rules §10.41): the orchestrator routes every review and delegates the mechanical half to the verifier subagent; name any area that instead deserves a DEDICATED reviewer agent (rare — each extra agent is a chat window the owner must steer). Optional and OUTSIDE the roster: an observer (.claude/agents/observer.md) — owner-triggered, never spawned or briefed by the orchestrator, no lane, writes only under reports/team/<owner-tag>/observer/. It critiques the rules and the process; the auditor checks compliance with them. Offer it; do not seed it as a lane.

Read the full file on GitHub · 142 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. 1mo ago Changed · +6 lines bcaad8fe1516
  2. 1mo ago Changed · +26 lines eeadda55b46a
  3. 2mo ago First seen · 110 lines · 69 tokens per session scan A 36d8a2023592

Subscribe to this mod's changes

keel-agent-team-create is a skill published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,940 once invoked, about $0.0003 per session on Opus 5.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.