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/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/agents/muratsilahtaroglu/claude-code-starter-kit/readme)<a href="https://agentmods.dev/agents/muratsilahtaroglu/claude-code-starter-kit/readme"><img src="https://agentmods.dev/badge/agents/muratsilahtaroglu/claude-code-starter-kit/readme/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/agents/muratsilahtaroglu/claude-code-starter-kit/readme"><img src="https://agentmods.dev/badge/agents/muratsilahtaroglu/claude-code-starter-kit/readme.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.00000 | $0.00442 |
| Opus 5.5 | $0.00000 | $0.00177 |
| Sonnet 5.5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
README 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
.claude/agents/ — reusable subagents
Subagents are isolated assistants for side tasks (deep research, audits, verification) that would
clutter the main thread with intermediate results you won't reference again. Each runs in its own
context window and returns only its final message to the parent — so the raw exploration never enters
your main context. Called via the Agent tool (by name); defined here as a markdown file with name /
description / optional tools / model frontmatter + a system-prompt body.
Shipped with the kit:
researcher— cited prior-art scout (web + local repo); backs rules.md §8 and/keel-research.verifier— adversarial fact-checker (CONFIRMED / REFUTED / UNCERTAIN); backs rules.md §4.auditor— read-only rules-compliance spot-check over a commit range; backs/keel-audit(the SessionStart hook nudges when one is due).observer— OWNER-triggered outside eye, never spawned by the orchestrator: critiques the process and the rules themselves (compliance is the auditor's axis, critique is this one's), writes only underreports/team/<owner-tag>/observer/, and opens every round with what became of the LAST round's findings plus its own refuted/total ratio. Field-earned on a 5-agent team (2026-09-05/06): 30 recommendations were evaluated and none tracked until the follow-up duty existed.
Add project-specific subagents here as the project needs them — e.g. a regression-runner, a
migration-reviewer, a log-analyst. The set is meant to grow per project, not stay fixed. Keep
each agent's body focused; put "when to use it" in the description (that's what drives auto-selection).
Mechanism trade-offs (skill vs subagent vs rule vs hook): docs/steering.md.
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 Changed · +5 lines 38d3c2fa222f
- 1mo ago First seen · 19 lines · 0 tokens per session scan A 2c6c80f824bb
README is an agent published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 442 tokens. 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 agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.