waza: Skill for Claude Code

.github/skills/iterative-retrieval/SKILL.md

iterative-retrieval is a skill for Claude Code, Codex from microsoft/waza. It costs 34 tokens per session (1,385 once invoked), scanned A, a copy of iterative-retrieval, MIT.

A structured method for giving sub-agents scoped tasks and checking their results. It limits each task to three cycles and requires the prompt to explain the task, its purpose, success conditions, and escalation path.

In plain words
What is it for?
Use it when spawning sub-agents for bounded work, defining acceptance criteria, handling blockers, and validating the result before closing an issue.
Why use it?
It reduces vague handoffs, repeated work, and unreviewed outputs when one agent asks another agent to do part of a job.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

This is microsoft/waza's own configuration. It tells Claude Code and Codex how to work on waza itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything waza configures →

About the project

microsoft/waza is a Go command-line tool for building and evaluating AI agent skills through test suites, benchmarks, and model comparisons. It is for developers who need to measure and improve how reliably agent skills work. The catalogue entries are Waza's own skills, instructions, agent, and MCP integration.

microsoft/waza · 1,424 stars · on GitHub · microsoft.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/waza. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/microsoft/waza/main/.github/skills/iterative-retrieval/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/waza

Made for: Claude Code, Codex.

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 iterative-retrieval

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/waza/iterative-retrieval/github.svg)](https://agentmods.dev/skills/microsoft/waza/iterative-retrieval)
Your own site
<a href="https://agentmods.dev/skills/microsoft/waza/iterative-retrieval"><img src="https://agentmods.dev/badge/skills/microsoft/waza/iterative-retrieval/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.

agentmods 80×15 button for iterative-retrieval

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/waza/iterative-retrieval"><img src="https://agentmods.dev/badge/skills/microsoft/waza/iterative-retrieval.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,385 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00034 $0.01385
Opus 5.5 $0.00014 $0.00554
Sonnet 5.5 $0.00007 $0.00277
Haiku 4.5 $0.00003 $0.00138

Measured 5d ago against content hash a1ac94cbaed7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

iterative-retrieval 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 5d 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.

Origin

This is a copy

100% identical to iterative-retrieval — 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.

.github/skills/iterative-retrieval/SKILL.md · 166 lines

How it starts

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

Iterative Retrieval Skill

Squad agents frequently spawn sub-agents to complete scoped work. Without structure, these handoffs become vague, cycles multiply, and outputs land without being checked. The Iterative Retrieval Pattern caps cycles at 3, mandates WHY context in every spawn, and requires the coordinator to validate agent output before closing an issue.


Spawn Prompt Template

Every agent spawn must include the following four sections. Copy and fill in the template:

## Task
{What you need done — concrete and bounded}

## WHY this matters
{The motivation and context. What system or user goal does this serve? What breaks if skipped?}

## Success criteria
{How you will know the output is correct. Be explicit — list acceptance criteria, not vibes.}
Example:
- [ ] File X exists and contains Y
- [ ] No regressions in existing tests
- [ ] PR is open targeting main with description matching the issue

## Escalation path
{What the agent should do if uncertain or stuck. "Stop and ask me" is valid.}
Example:
- If requirements are ambiguous → stop, comment on the issue, set label status:needs-decision
- If blocked by a dependency → label status:blocked, explain in a comment
- If 3 cycles exhausted without resolution → write a summary to inbox and surface to coordinator

3-Cycle Protocol

Cycle Description Exit condition
1 Initial attempt Done → coordinator validates. Incomplete → surface delta.
2 Targeted retry with specific corrections Done → coordinator validates. Incomplete → one more.
3 Final attempt with all context from cycles 1–2 Done or escalate — no cycle 4.

Rules

  1. After each cycle, the coordinator evaluates the output against the success criteria before accepting it or spawning the next cycle.
  2. Objective context forward: each subsequent spawn includes a summary of what was tried and what is still missing — not just a repeat of the original task.
  3. Cycle 3 exhausted → escalate: write a summary to .squad/decisions/inbox/, label the issue status:needs-decision, and notify the user.

Read the full file on GitHub · 166 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. 5d ago First seen · 166 lines · 34 tokens per session scan A a1ac94cbaed7

Subscribe to this mod's changes

iterative-retrieval is a skill published in the GitHub repository microsoft/waza (1,424 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,385 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to iterative-retrieval, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories