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 skills/muratsilahtaroglu/claude-code-starter-kit/keel-updatenpx skills add muratsilahtaroglu/claude-code-starter-kit --skill keel-updategit 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-update)<a href="https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-update"><img src="https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-update.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.00068 | $0.02008 |
| Opus 5 | $0.00034 | $0.01004 |
| Sonnet 5 | $0.00014 | $0.00402 |
| Haiku 4.5 | $0.00007 | $0.00201 |
Grade C, and why
keel-update scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/keel-latest # idempotent — clear the stale clone a previous /keel-update run left behind How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/keel-update — sync this project with the latest Keel template
Use when the kit was cloned a while ago and the template has since improved (hardened hooks, doc
fixes, workflow updates). Pull model: run it IN the project, review diffs, approve. Non-destructive is
the hard rule (same spirit as /keel-adopt): nothing is applied without a shown diff + an explicit yes.
One channel: the kit is clone-only (the plugin/marketplace half was retired in v0.8.23 — it
delivered only the tooling, double-fired hooks alongside a clone, and needed marketplace access that
locked-down networks block). Everything therefore syncs HERE, through the buckets below. If a project
still has keel@keel installed from before, removing it is the fix for double-firing hooks.
1. Fetch the latest template (never inside the project)
rm -rf /tmp/keel-latest # idempotent — clear the stale clone a previous /keel-update run left behind
git clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kit /tmp/keel-latest
git -C /tmp/keel-latest rev-parse --short HEAD # record for the handover line
2. Classify every template path into three buckets
- PROTECTED — never touched (project-owned):
HANDOVER.md·LESSONS.md·TASKS.md·PLAN.md·docs/handover-archive.md·docs/lessons-retired.md·docs/architecture.md·docs/adr/*(except the kit-owned0000template and the folderREADME.md— those are TOOLING) ·CLAUDE.md·README.md·LICENSE·config/·requirements/*.{txt,lock}contents ·.env.examplevalues ·src/·tests/(except the kit-ownedtests/unit/test_keel_*.pymatrix — that is TOOLING, same carve-out as the ADR0000template; never put project tests in atest_keel_*.pyfile) ·scratch/·research/findings ·reports/·.claude/last-audit·.claude/project-owner·.claude/keel-caps·.claude/lessons-backlog·.claude/tasks-backlog(project state: audit clock + governance owner + tuned caps + entry-budget baseline) ·.claude/agents/team-*.md(project agent-team charters, owner-authored — the kit ships none;.claude/agent-team-sessionsis git-ignored and never syncs). - REVIEW — likely tailored; full diff, apply hunk-by-hunk with approval:
rules.md·.claude/settings.json(permissions merge = union, keep the project's) ·.gitignore·.pre-commit-config.yaml·pyproject.toml·Makefile·Dockerfile*·.dockerignore·docker-compose.yml·.editorconfig·.github/*(workflows + PR template) ·docs/layouts.md·docs/user_manual.md· folder READMEs that carry KIT DOCTRINE inside a PROTECTED tree —scratch/README.md,tests/README.md,tests/*/README.md: the folder's CONTENTS are the project's, but the README states the kit's rule for that folder and projects tailor it, so it is diffed hunk-by-hunk rather than skipped with the tree (without this the scratch-as-evidence rule of v0.8.25 could never reach an adopted project). - TOOLING — template-owned; summarize changes, one approval for the batch:
.claude/skills/**·.claude/hooks/**·.claude/agents/{researcher,verifier,auditor,README}.md·.claude/rules/README.md(+ example) ·tests/unit/test_keel_*.py·docs/security.md·docs/steering.md·docs/adr/0000-adr-template.md·docs/adr/README.md·docs/assets/·CONTRIBUTING.md(kit-meta by its own first line) · folderREADME.mds.
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 Changed 9a954b05cded
- 5d ago First seen · 98 lines · 68 tokens per session scan C 0305d2f61f0c
keel-update is a skill published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 2,008 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.