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 agentmods add skills/0xagentkitchen/kitchenloop/loop-review-metanpx skills add 0xagentkitchen/kitchenloop --skill loop-review-metagit clone --depth 1 https://github.com/0xagentkitchen/kitchenloopWrote 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/0xagentkitchen/kitchenloop/loop-review-meta)<a href="https://agentmods.dev/skills/0xagentkitchen/kitchenloop/loop-review-meta"><img src="https://agentmods.dev/badge/skills/0xagentkitchen/kitchenloop/loop-review-meta.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01898 |
| Opus 5 | $0.00000 | $0.00949 |
| Sonnet 5 | $0.00000 | $0.00380 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
loop-review-meta 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 3d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loop Review Meta
Macro analysis across all loop review reports -- trends, recurring themes, systemic recommendations.
Triggers
loop review metameta analysis
Overview
Loop Review Meta is a higher-order analysis that reads ALL loop review reports and identifies patterns that span multiple review periods. While individual loop reviews catch per-iteration issues, the meta review catches systemic trends: recurring themes that never get fixed, drift in loop behavior, effectiveness of self-improvement over time.
Procedure
Step 1: Gather All Review Reports
-
Load
kitchenloop.yaml-- readpaths. -
List all review reports in
{paths.reports}/:ls {paths.reports}/loop-review-iter-*.md -
Read each report. Extract structured data:
- Iteration range covered
- Metrics (pass rate, test count, backlog, PRs merged)
- Finding counts by severity (Blocker, Important, Observation)
- Recommendations made
- External auditor results
-
Read loop state at
paths.loop_statefor the full iteration history.
Step 2: Trend Analysis
2a. Quality Trends
Plot (textually) how key metrics have evolved across all review periods:
- Pass rate trajectory: Is it trending up (loop is improving the codebase), flat (loop is maintaining), or down (loop is introducing regressions)?
- Test count trajectory: Growing (good coverage expansion), shrinking (test deletion or skip-creep), or flat?
- Backlog trajectory: Growing (more issues found than fixed), shrinking (good execution velocity), or stable?
2b. Finding Recurrence
Identify findings that appear across multiple review reports:
- Cluster findings by theme (e.g., "test coverage gaps", "error handling", "documentation drift", "convention violations").
- For each theme, count how many review periods it appeared in.
- Flag themes that appear in 3+ reviews as Systemic Issues.
2c. Recommendation Follow-Through
For each recommendation made in previous reviews:
- Was it converted to a ticket?
- Was the ticket resolved?
- Did the issue recur after the fix?
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.
- 3d ago First seen · 272 lines · 0 tokens per session scan A 4a1058da3539
loop-review-meta is a skill published in the GitHub repository 0xagentkitchen/kitchenloop (23 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,898 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…