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.
git clone --depth 1 https://github.com/byerlikaya/claude-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/commands/byerlikaya/claude-starter-kit/update-csk)<a href="https://agentmods.dev/commands/byerlikaya/claude-starter-kit/update-csk"><img src="https://agentmods.dev/badge/commands/byerlikaya/claude-starter-kit/update-csk/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.
<a href="https://agentmods.dev/commands/byerlikaya/claude-starter-kit/update-csk"><img src="https://agentmods.dev/badge/commands/byerlikaya/claude-starter-kit/update-csk.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00594 |
| Opus 5.5 | $0.00010 | $0.00238 |
| Sonnet 5.5 | $0.00005 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
update-csk 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.
What it actually says
/update-csk
Bring the installed kit up to the latest published version:
- Detect install type. If
.claude/VERSIONexists → a full install (steps below). If the kit runs as a plugin (no.claude/VERSION), it updates through the plugin system — tell the user to runclaude plugin update claude-starter-kitand stop here. - Current version: read
.claude/VERSION. - Latest version:
npm view @byerlikaya/claude-starter-kit version(needs network). If it can't be reached, say so and stop — don't guess. - Compare. Already on the latest → report "up to date (vX)" and stop. Otherwise show old → new.
- Update — this rewrites the kit-owned files under
.claude/(your./CLAUDE.mdand project skills are preserved). Show this plan first, then run:npx --yes @byerlikaya/claude-starter-kit@latest update --here --yes. Two DIFFERENT--yesflags, both required for a non-interactive run: the one before the package name is npx's own — it auto-confirms npx'sOk to proceed?install prompt, which reads the real TTY and IGNORES piped input, so without it the command hangs before the kit even starts. The--here --yesafter the package go to the updater (--here= apply on the current branch,--yes= accept the smart defaults). Together they let it run to completion instead of blocking on a prompt your shell can't answer. If you'd rather review each handover decision yourself, tell the user to runnpx @byerlikaya/claude-starter-kit@latest update(no flags) in their own terminal, where both the npx and the interactive prompts work. - Verify: run
/doctor-csk(orbash .claude/eval/doctor.sh) so a bad/partial update surfaces immediately. - Report old → new + the headline changes (from the release notes / CHANGELOG).
- Reload (manual — a command can't do it itself): the discipline in the running session is still the OLD one.
Tell the user to run
/compact(or/clear) so the updated.claude/DISCIPLINE.mdis re-read in the same session — no restart needed.
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.
- 1mo ago First seen · 28 lines · 24 tokens per session scan A fb3fead5d904
update-csk is a command published in the GitHub repository byerlikaya/claude-starter-kit (24 stars, last pushed 29d ago), licensed MIT. It adds 24 tokens to every session and 594 once invoked, about $0.0001 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-30.
Other commands, from other repositories
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
refactor
Analyze code for SOLID violations and suggest targeted improvements.