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 skills add muratsilahtaroglu/claude-code-starter-kit --skill keel-teamgit clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kitWrote 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/skills/muratsilahtaroglu/claude-code-starter-kit/keel-team)<a href="https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-team"><img src="https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-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.00077 | $0.01308 |
| Opus 5 | $0.00039 | $0.00654 |
| Sonnet 5 | $0.00015 | $0.00262 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
keel-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/keel-team — set up the human team (owner-only)
When: helpers are joining a solo project — different PEOPLE on different MACHINES sharing a
repo/host. This wizard INSTALLS the existing Multi-user discipline (docs/steering.md "Multi-user",
rules §10.40–41, review-v2) in one approved pass — it invents nothing new. Same-machine AGENT
sessions are /keel-agent-team-create's job; the two coexist: human lanes and agent lanes share one
TASKS board, and setup authority is the owner's in both.
0. Owner gate
.claude/project-ownerexists andgit config user.name≠ its content → STOP ("team setup is the owner's — ask @").- Missing → this run DECLARES ownership: ask the owner's exact
git config user.name, write the file (one line). State the identity invariant for everyone: repo-localgit config user.name "<tag>", single token, byte-for-byte the repo's@tagspelling — a mismatch silently unarms every ownership mechanism (the reground hook nags when unset).
1. Interview the owner
- Members — each person's
@tag(= their git user.name) + a one-line area/responsibility- a task-id prefix: 2–4 lowercase letters, unique across the whole roster (agents included),
fixed for good. Their items run
<prefix>1 · <prefix>2 …, and the same id names their reports (reports/team/<@tag>/<id>_fix_<date>.md) and anyscratch/<id>/probe. Ids are never renamed or reused — permanent artifacts cite them (rules §9.32, §10.40). One case only: a series split acrossr1andR28makes every count wrong (field case).
- a task-id prefix: 2–4 lowercase letters, unique across the whole roster (agents included),
fixed for good. Their items run
- Contribution model (§6.17 — host reality decides the wall): same-repo branch→PR · fork→PR (developers Read-only) · no-remote/local-only. Walk the HOST-wall table (steering "Multi-user") and say which wall actually ENFORCES here — on a free private PERSONAL repo there is NO real wall: either move to a free org (Read + fork PRs) or accept discipline-only and write that into the team doc.
- Caps — propose
.claude/keel-capssized to headcount (5 people ≈HANDOVER=200·HANDOVER_BLOCKS=4·LESSONS=400·TASKS=250— field-tested values; the owner tunes). Pinned only on approval, never silently (§10.40). - CI shape (when PRs gate merges): §7.24 secret-less gating — a fork PR receives NO repo
secrets, so live-cred/network tests must SKIP, never fail. If bootstrap pruned
.github/, team scale-up is the moment the prune reverses — as a recorded ADR addendum.
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.
- 7d ago First seen · 69 lines · 77 tokens per session scan A 5391c083ea7b
keel-team is a skill published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,308 once invoked, about $0.0004 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.
Other skills, from other repositories
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
approval-workflows
Configure ServiceNow approval rules and sysapprovalapprover records — manager/group/script approvers, multi-level routing, delegation via sysuserdelegate, and parent-record state rollup.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
field-service
Build ServiceNow Field Service Management — wmorder work orders, wmtask tasks, wmresource technicians with skills/territories, dispatch/auto-assignment, mobile status updates, and time entries.
hr-service-delivery
Build ServiceNow HR Service Delivery — snhrcorecase from Employee Center or HR catalog, snhrlelifecycleevent onboarding/offboarding with templated activities, and HR document generation.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.