agentmods.dev

iterate

iterate is a skill for Claude Code, Codex from stellarshenson/claude-code-plugins. It costs 48 tokens per session (1,075 once invoked), scanned A, original, MIT.

A review skill that applies fixes based on identified concerns, saves a numbered document version, and measures the remaining risk again.

In plain words
What is it for?
Use it to choose between suggested, automatic, or planned fixes, update a document, and re-score its concerns.
Why use it?
It keeps improvements traceable and tests whether each revision addresses the problems found in review.

Skill for Claude CodeCodex

Part of the devils-advocate plugin — 4 skills, 3 commands, 2 agents shipped together

not rated 3 4d ago A scan 48 tokens original MIT
View the source file stellarshenson/claude-code-plugins
Install

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.

agentmods
npx agentmods add skills/stellarshenson/claude-code-plugins/iterate
Any agent
npx skills add stellarshenson/claude-code-plugins --skill iterate
Clone the repo
git clone --depth 1 https://github.com/stellarshenson/claude-code-plugins

Made for: Claude Code, Codex.

Or install devils-advocate, the plugin that ships this one along with the rest of its 4 skills, 3 commands, 2 agents.

Wrote 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.

agentmods badge for iterate

README.md
[![agentmods](https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/iterate.svg)](https://agentmods.dev/skills/stellarshenson/claude-code-plugins/iterate)
Your own site
<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/iterate"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/iterate.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,075 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.01075
Opus 5 $0.00024 $0.00537
Sonnet 5 $0.00010 $0.00215
Haiku 4.5 $0.00005 $0.00108

Measured 3d ago against content hash eba8dfb9c0e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

plugins/devils-advocate/skills/iterate/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Devil's Advocate - Iterate

One cycle: improve, version, score, rename with residual.

Task Tracking

MANDATORY: Use TaskCreate/TaskUpdate per step (decide, apply, score, finalize, update). Mark in_progress/completed.

Prerequisites: devils_advocate.md must have scorecard with top gaps. Otherwise run /devils-advocate:evaluate first.

Step 1: Decide how to improve

ASK:

"Top concerns by residual risk: [list top 5 from latest scorecard]

How to address them?

  1. Your suggestions - tell me what to change
  2. Auto-apply - I apply recommended options from scorecard
  3. Planning mode - discuss each concern before changing
  4. You already edited - skip to re-scoring (external edits)

Which? (or mix: 'auto for #1-3, discuss #4')"

Step 2: Apply changes + create version

If user chose 1, 2, or 3 (AI makes changes):

  1. Determine next version - scan existing <name>_v*.md
  2. Copy current as <name>_v<NN>.md (no score suffix yet)
  3. Apply changes:
    • Mode 1: user's suggestions
    • Mode 2: recommended options from top gaps
    • Mode 3: agreed changes from planning
  4. Track concerns each change targets
  5. Track cross-concern tensions - some fixes break others: answering "why" may increase finger-pointing; adding evidence may increase verbosity; SOW quotes may increase defensive tone; brevity may drop supporting evidence; stronger language may improve facts but worsen tone

If user chose 4: skip to Step 3. User's document IS current state.

Step 3: Score

Re-read document in full.

ASK: "Score in-session or standalone (claude -p)?"

  • In-session: score here, show reasoning
  • Standalone: run via claude -p with persona + document

Per concern:

  1. Re-score 0-100% against current text
  2. Document: "Score X% -> Y% because [specific text change]"
  3. Add new concerns from changes
  4. Recalculate total residual

Step 4: Finalize version

If AI made changes (versioned copy exists):

  1. Embed scorecard at end: 
    ---

## Document Scorecard (Devil's Advocate)

**Persona**: [devil role and key bias]
**Score**: [total residual risk] (lower = better, max [total absolute risk])

| # | Concern | Risk | Score | Residual | How addressed |
|---|---------|------|-------|----------|---------------|
| 1 | [name] | [risk] | [0-100%] | [residual] | [specific text] |

Read the full file on GitHub · 109 lines

Changes

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.

  1. 3d ago First seen · 109 lines · 48 tokens per session scan A eba8dfb9c0e7

Subscribe to this mod's changes

iterate is a skill published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,075 once invoked, about $0.0002 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-31.

Code reviewWriting and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens