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/.cursor/skills/iterate-feature.mdcgit 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/rules/janekbaraniewski/openusage/iterate-feature)<a href="https://agentmods.dev/rules/janekbaraniewski/openusage/iterate-feature"><img src="https://agentmods.dev/badge/rules/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/rules/janekbaraniewski/openusage/iterate-feature"><img src="https://agentmods.dev/badge/rules/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.00027 | $0.00173 |
| Opus 5.5 | $0.00011 | $0.00069 |
| Sonnet 5.5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00003 | $0.00017 |
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
@docs/skills/iterate-feature/SKILL.md contains the full skill specification. Read and follow it completely.
The user's request is to iterate on the feature "$ARGUMENTS".
Follow all phases in order:
- Phase 0: Load context — design doc, feedback sources, changed files
- Phase 1: Triage issues by priority (P0–P3)
- Phase 2: Plan iterations with approach and risk
- Phase 3: Execute fixes with per-fix verification
- Phase 4: Re-validate (build, tests, design compliance)
- Phase 5: Iteration summary with 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 · 18 lines · 27 tokens per session scan A c20cbaedd495
iterate-feature is a cursor rule published in the GitHub repository janekbaraniewski/openusage (235 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 173 once invoked, about $0.0001 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 cursor rules, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
techdebt
Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions.
code-change-refactor
This rule applies when refactoring existing code to improve quality, adopt new patterns, or integrate with newly created functionality.
validator_quality
Quality Validator — check for complexity, dead code, inconsistent naming, and technical debt.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.