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 ash1794/vibe-engineering --skill iteration-reviewgit clone --depth 1 https://github.com/ash1794/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/ash1794/vibe-engineering/iteration-review)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/iteration-review"><img src="https://agentmods.dev/badge/skills/ash1794/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/ash1794/vibe-engineering/iteration-review"><img src="https://agentmods.dev/badge/skills/ash1794/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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-iteration-review — 100% identical, 0 lines differ
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 ash1794/vibe-engineering (10 stars, last pushed 3mo ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…