Borrowing it
Nothing to install: this file belongs to janekbaraniewski/openusage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/janekbaraniewski/openusage/main/.claude/commands/iterate-feature.mdgit clone --depth 1 https://github.com/janekbaraniewski/openusageWrote 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/commands/janekbaraniewski/openusage/iterate-feature)<a href="https://agentmods.dev/commands/janekbaraniewski/openusage/iterate-feature"><img src="https://agentmods.dev/badge/commands/janekbaraniewski/openusage/iterate-feature/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/commands/janekbaraniewski/openusage/iterate-feature"><img src="https://agentmods.dev/badge/commands/janekbaraniewski/openusage/iterate-feature.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.00000 | $0.00144 |
| Opus 5.5 | $0.00000 | $0.00058 |
| Sonnet 5.5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
iterate-feature 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.
What it actually says
Iterate on the feature "$ARGUMENTS" to fix issues and address feedback.
Read and follow the full skill specification in docs/skills/iterate-feature/SKILL.md.
Follow all phases:
- Phase 0 — Load: Find design doc, gather feedback.
- Phase 1 — Triage: Categorize issues by priority.
- Phase 2 — Plan: Identify files and approach for each fix.
- Phase 3 — Execute: Fix, test, verify each issue.
- Phase 4 — Re-validate: Build, test, check compliance.
- Phase 5 — Summary: Report fixes and verdict.
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 · 13 lines · 0 tokens per session scan A 4d89614d7fcc
iterate-feature is a command published in the GitHub repository janekbaraniewski/openusage (235 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 144 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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
fix
Universal debugging and fix application with semantic code analysis.
debug
Start GDB debug session with OpenOCD or probe-rs.