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 agents/muratsilahtaroglu/claude-code-starter-kit/readmegit clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kitWhat 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 | $0.00000 | $0.00325 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 2d 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).
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.
- 2d 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 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 325 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
ARCHITECTURE
Agent "ARCHITECTURE" from Tura-AI/tura, covering agents crate architecture, current layout, runtime loading, agent config and manual agent configuration.
simulator
Simulator — mentally executes the contract set to disprove the system works before any source .py is written.
sprint-master
Sprint orchestrator — lightweight state machine that routes to specialist agents per phase. Use with claude --agent sprint-master or via sprint-runner.
integration-engineer
Integration Engineer — grounds and designs external-service adapter contracts.
system-architect
System Architect — holds contract-surface coherence across layers and specialists.
ux-engineer
UX Engineer — designs the user-facing contract and interaction flows.