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 SZoloth/skill-pack --skill iterategit clone --depth 1 https://github.com/SZoloth/skill-packWrote 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/szoloth/skill-pack/iterate)<a href="https://agentmods.dev/skills/szoloth/skill-pack/iterate"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/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/szoloth/skill-pack/iterate"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/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.00073 | $0.01378 |
| Opus 5.5 | $0.00029 | $0.00551 |
| Sonnet 5.5 | $0.00015 | $0.00276 |
| Haiku 4.5 | $0.00007 | $0.00138 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/iterate — Diverge, Compare, Converge
Spin up N parallel agents on isolated git worktrees, each exploring a different direction for the same problem. Review all variants, pick the best, merge it back.
When to Use
- User wants to explore multiple approaches to a problem
- Design/UI work where visual comparison matters
- Refactoring where there are multiple valid strategies
- Any task where "try a few things and pick the best" is the right move
Prerequisites
- Must be inside a git repository with a clean working tree (or stashable changes)
- The repo should have committed state to branch from
Usage
/iterate <task description>
/iterate 3 <task description> # explicit count (default: 3)
/iterate 2 redesign the settings page using shadcn
How It Works
Phase 1: Parse Arguments
Parse $ARGUMENTS to extract:
- N (number of variants): First token if it's a number 1-5, otherwise default to 3
- Task: Everything after the count (or all of $ARGUMENTS if no count)
If no arguments provided, ask the user:
- What task/problem should the agents explore?
- How many variants? (default 3)
Phase 2: Generate Divergent Angles
Before spawning agents, generate N distinct approaches. These should be meaningfully different, not just cosmetic variations.
Example for "redesign the settings page":
- Minimal — strip to essentials, single scrollable page, maximum whitespace
- Tabbed — group settings into logical tabs with a sidebar nav
- Search-first — spotlight-style search with categorized results
Example for "implement caching":
- In-memory LRU cache with TTL
- Redis-backed with cache invalidation events
- Service worker + Cache API for edge caching
Present the angles to the user for approval before spawning. The user may adjust, add, or remove angles.
Phase 3: Spawn Agents
For each variant, spawn an agent using:
Agent tool with:
- isolation: "worktree"
- subagent_type: "general-purpose"
- run_in_background: true (to run all N in parallel)
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 · 160 lines · 73 tokens per session scan A d5f4e78244fc
iterate is a skill published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,378 once invoked, about $0.0003 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 skills, from other repositories
changelog-generator
Convierte un git log, lista de commits o notas de lanzamiento en un changelog pulido orientado al usuario. Usa cuando estés escribiendo notas de versión, generando una entrada en CHANGELOG.md o documentando qué cambió en una versión. Produce una sección de changelog estructurada con encabezado de versión, cambios…
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using the rationale recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address…
update-pr
Update an existing GitHub pull request's title and description to reflect the current state of the branch. Use when the user asks to "update the PR", "update PR description", "update PR title", "refresh PR description", or "sync PR with changes".
release-notes-from-git-log
Turn a git log into user-facing release notes grouped by feature and fix. Use when asked for release notes from this git log, a changelog entry from these commits, or to turn commits into release notes. Produces a grouped changelog with one line per change and a short headline.
create-pr
Create a GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "create a pull request", "open a PR", or "submit a PR".