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 mhylle/claude-skills-collection --skill iterate-plangit clone --depth 1 https://github.com/mhylle/claude-skills-collectionWrote 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/mhylle/claude-skills-collection/iterate-plan)<a href="https://agentmods.dev/skills/mhylle/claude-skills-collection/iterate-plan"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/iterate-plan/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/mhylle/claude-skills-collection/iterate-plan"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/iterate-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00116 | $0.03110 |
| Opus 5 | $0.00058 | $0.01555 |
| Sonnet 5 | $0.00023 | $0.00622 |
| Haiku 4.5 | $0.00012 | $0.00311 |
Grade A, and why
iterate-plan 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 12d 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 — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterate Plan
Overview
This skill enables intelligent iteration on existing implementation plans. Rather than rewriting plans from scratch, it makes surgical, well-researched updates while preserving the plan's existing structure and quality standards.
Progress Tracking with Task Tools
This skill uses Claude Code's native Task tools for progress tracking.
When iterating on plans, you must keep Tasks synchronized with plan changes:
| Plan Change | Task Action |
|---|---|
| Add new phase | TaskCreate for new phase, update addBlockedBy dependencies |
| Remove phase | TaskUpdate to mark removed (or delete if not started) |
| Reorder phases | Update addBlockedBy relationships |
| Rename phase | TaskUpdate to change subject |
| Modify phase scope | TaskUpdate to change description |
Important: The plan's task_list_id in metadata links to its Tasks. Always verify you're updating the correct task list.
Migrating Old Plans to Task Tools
Use this process when a plan lacks
task_list_idin its metadata.
Old plans used checkbox-based progress tracking ([x] / [ ]). The new system uses Task tools. When you encounter an old plan, migrate it.
Detecting Old Plans
An old plan has:
- No
task_list_idin YAML frontmatter - Checkbox-based progress:
- [x] Task completed/- [ ] Task pending - No reference to Task tools
Migration Process
Step M1: Generate task_list_id
Create an ID from the plan filename:
docs/plans/2024-03-15-user-auth.md → plan-2024-03-15-user-auth
docs/plans/api-refactor.md → plan-api-refactor
Step M2: Add metadata to plan
Add or update the YAML frontmatter:
---
task_list_id: plan-2024-03-15-user-auth
migrated_from_checkboxes: true
migration_date: 2026-01-25
---
Step M3: Create Tasks for each phase
For each phase in the plan:
TaskCreate:
subject: "Phase N: [Phase Name]"
description: "[Phase objective from plan] - Plan: [plan file path]"
activeForm: "Implementing Phase N: [Name]"
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.
- 12d ago First seen · 432 lines · 116 tokens per session scan A 874fb04eb0e9
iterate-plan is a skill published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 9d ago), licensed MIT. It adds 116 tokens to every session and 3,110 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…