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 skills add byerlikaya/claude-starter-kit --skill iterategit 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/skills/byerlikaya/claude-starter-kit/iterate)<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/iterate"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/iterate/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/skills/byerlikaya/claude-starter-kit/iterate"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/iterate.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.00028 | $0.00698 |
| Opus 5 | $0.00014 | $0.00349 |
| Sonnet 5 | $0.00006 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
iterate 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterate — refine to Done, don't stop at the first attempt
Trigger phrases: "iterate", "loop until done", "keep going until"
When
A task has an objective acceptance criterion (tests, a review gate, a spec) and the first attempt may not
meet it. This is a single-session refinement loop — NOT the harness /loop, which schedules a prompt on an
interval. Open-ended exploration with no checkable target does not belong here.
The loop
- Name the exit test first — the concrete, checkable condition that means "done": tests green,
review-agent-cskclean, the spec's acceptance criterion met, zero SonarQube findings. No exit test → go to spec-planning first; a loop without a target never terminates. Prefer an external, machine-grounded verifier — a test exit code, a schema match, a lint/quality gate — over an LLM's self-assessment. A model grading its own output inflates; an "it looks done" or even a single "review clean" with no objective check is a weak verifier. When the only available check is a judgment call, ground it (a second agent with a distinct lens, an explicit rubric) rather than trusting the loop's own say-so. For a generative task with no exit code, theeval-graderskill is that external verifier — a two-layer scorecard (code metrics + LLM-judge) over a fixed set, read as signed deltas vs a pinned baseline. - Run one round: change → verify (drive the real flow, not only tests) → check the exit test.
- Report the gap every round — state what still fails and why. Never loop silently.
- Repeat until the exit test passes. Stop early and surface it if: two rounds pass with no new progress (you are stuck — report, don't spin), the exit test itself is wrong, or a blocker needs a decision from the user.
- Close at the DoD gate, not at a commit.
commit-agent-cskstill proposes and waits for §4.4 approval. The loop never commits, pushes, or deploys on its own.
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.
- 10d ago First seen · 43 lines · 28 tokens per session scan A 631f4b4aca63
iterate is a skill published in the GitHub repository byerlikaya/claude-starter-kit (22 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 698 once invoked, about $0.0001 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-30.
Other skills, from other repositories
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
eval-harness
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles.
dependency-upgrade
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.