Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kitnpx agentmods add skills/muratsilahtaroglu/claude-code-starter-kit/keel-statsWrote 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-stats)<a href="https://agentmods.dev/skills/muratsilahtaroglu/claude-code-starter-kit/keel-stats"><img src="https://agentmods.dev/badge/skills/muratsilahtaroglu/claude-code-starter-kit/keel-stats.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.00062 | $0.00368 |
| Opus 5 | $0.00031 | $0.00184 |
| Sonnet 5 | $0.00012 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
keel-stats 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 6d 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
/keel-stats — see what ran, when, how often
The ritual-log hook records every Skill-tool call, user-typed command (custom = command …
via UserPromptExpansion; built-ins like /compact = typed /… via UserPromptSubmit — first
token only, user prose never logged), compact boundary, session start and hook BLOCK into
.claude/ritual-log (machine-local, git-ignored, self-trimmed). This skill renders it for humans.
- Run the deterministic generator — never parse the log by hand:
python3 .claude/ritual-report.py - Open / point the user at
reports/ritual-stats.md— the Mermaid timeline renders on GitHub and in the VSCode markdown preview: one colored box per interval (green = session start, amber = manual compact, red = auto compact; PLAN.md's palette), event counts inside, full detail in the table below it. - Quote the headline numbers (totals line) back to the user in one sentence.
- Scope honesty: the log is machine-local and trimmed to ~1000 lines — long-horizon history lives in git/HANDOVER, not here. Do not commit the report unless the user asks (it is a regenerable artifact; the compact-gate ignores it either way).
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.
- 6d ago First seen · 25 lines · 62 tokens per session scan A e0ff9c21bc95
keel-stats is a skill published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 368 once invoked, about $0.0003 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
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
mle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
content-engine
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
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.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.