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 mracal/vibe-engineering --skill iteration-reviewgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/iteration-review)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/iteration-review"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/iteration-review/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/mracal/vibe-engineering/iteration-review"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/iteration-review.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.00034 | $0.00521 |
| Opus 5 | $0.00017 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
vibe-iteration-review 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 10d 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.
This is a copy
100% identical to vibe-iteration-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-iteration-review
What gets measured gets improved. Review every iteration.
When to Use This Skill
- End of a development sprint or iteration
- After completing a milestone
- Before starting the next iteration (retrospective)
- When the user asks "how did we do?"
When NOT to Use This Skill
- Mid-iteration (too early, incomplete data)
- After single small tasks
- When there's no defined iteration boundary
Steps
-
Gather data:
- What was planned for this iteration?
- What was actually delivered?
- How many commits? Lines changed? Tests added?
- Coverage delta? Quality metrics?
- Known issues introduced?
-
Grade quality (A-F):
- A: All planned work delivered, tests pass, no known issues, clean code
- B: Most work delivered, minor issues, good test coverage
- C: Core work delivered, some gaps, acceptable quality
- D: Significant gaps, quality issues, needs rework
- F: Iteration failed, major rework needed
-
Compare to previous iterations (if available):
- Is quality trending up or down?
- Is velocity improving?
- Are known issues accumulating?
-
Extract lessons:
- What went well?
- What went poorly?
- What to change next iteration?
Output Format
Iteration Review: [Iteration Name/Number]
Quality Grade: A/B/C/D/F Planned vs Delivered: X/Y (Z%)
| Metric | This Iteration | Previous | Trend |
|---|---|---|---|
| Commits | X | Y | ↑/↓/→ |
| Tests added | X | Y | ↑/↓/→ |
| Coverage | X% | Y% | ↑/↓/→ |
| Known issues | X | Y | ↑/↓/→ |
Delivered
- [Task 1]
- [Task 2]
- [Task 3] — deferred because [reason]
Lessons Learned
- [What to continue]
- [What to change]
- [What to stop]
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.
- 10d ago First seen · 73 lines · 34 tokens per session scan A 45e0fd890a37
vibe-iteration-review is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 521 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-iteration-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
code-intelligence-contract
Use when dependency, call-chain, blast-radius, architecture, domain-flow, or unfamiliar-codebase analysis needs an optional vendor-neutral code-intelligence provider.
lua-client-server-contract-audit
Use when normalized Lua client/server RPC contract copies or generated protocol tables disagree on opcode, request-response fields, types, ordering, or source authority.
mmorpg-packet-protocol-review
Use when a C++ server and Unity client protocol manifest or wire compatibility review covers packet version negotiation, numeric opcode registry, byte layout order, direction, and request-response pairing.
review-swarm
Use when reviewing a known change set through parallel read-only code, architecture, test, safety, or product lanes with disjoint concerns and one integrator verdict.
codebase-sync
Convention discovery and rule generation from codebase analysis. Scans project structure, builds search indexes, identifies patterns, and generates enforceable rules.
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.