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 ntorga/agent-starter-kit --skill review-loopgit clone --depth 1 https://github.com/ntorga/agent-starter-kitWrote 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/ntorga/agent-starter-kit/review-loop)<a href="https://agentmods.dev/skills/ntorga/agent-starter-kit/review-loop"><img src="https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/review-loop/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/ntorga/agent-starter-kit/review-loop"><img src="https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/review-loop.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.00019 | $0.01222 |
| Opus 5 | $0.00010 | $0.00611 |
| Sonnet 5 | $0.00004 | $0.00244 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
review-loop 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
This skill defines how the Maestro reviews sub-agent work before it reaches the user. Two modes serve different needs. Incremental reviews (per epic) use one reviewer. Full branch reviews (at feature completion) dispatch three reviewers for full coverage.
Procedure
-
Determine mode.
- Incremental (default) — used for per-epic reviews during plan execution.
- Full branch — used when all epics in
impl.mdare marked ✓ and the review covers the entire branch's accumulated changes. Triggered byskills/plan-management/SKILL.md→ Tracking Progress.
-
Identify scope. Determine the changed files. Use the command matching the current mode:
- Incremental — files changed since the last commit:
git diff HEAD --name-only; git ls-files --others --exclude-standard - Full branch — files changed against the base branch:
git diff "$(git merge-base HEAD main)" --name-only; git ls-files --others --exclude-standard
If no files changed, skip the review loop.
- Incremental — files changed since the last commit:
-
Dispatch. Dispatch the reviewer (
personas/reviewer.md) (follows:skills/dispatch/SKILL.md).Incremental mode — single dispatch. Reviewer runs all three lenses.
Full branch mode — three dispatches with focused
<task>:- First: coherence focus (follows:
skills/code-coherence-review/SKILL.md). - Second: quality focus (follows:
skills/code-quality-review/SKILL.md). - Third: security focus (follows:
skills/code-sec-review/SKILL.md).
For plans and non-code work, use a single dispatch regardless of mode.
The
<task>for every reviewer dispatch must include:- What was produced (artifact type and affected scope).
- The original
<task>or acceptance criteria. - For code: the list of changed files.
- The focus area (for Full branch mode).
- First: coherence focus (follows:
-
Merge findings. When all dispatched reviewers return:
- Union all blockers, warnings, and notes across all reviewers.
- Deduplicate identical entries — same file, same line, same issue counts once. Dedup before verify is intentional; step 5 verifies each remaining finding.
- If verdicts conflict, the stricter verdict wins.
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.
- 2d ago First seen · 83 lines · 19 tokens per session scan A 464371e72f62
review-loop is a skill published in the GitHub repository ntorga/agent-starter-kit (142 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 1,222 once invoked, about $0.0001 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-09-13.
Other skills, from other repositories
pragma-code-review
A code-review guide written in Chinese. It reviews code across correctness, architectural boundaries, risk, and verification.
safe-refactor
Refactor checklist with guardrails.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.