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/pallerana/agentic-loop-engineering-kit/loop-verifiernpx skills add pallerana/agentic-loop-engineering-kit --skill loop-verifiergit clone --depth 1 https://github.com/pallerana/agentic-loop-engineering-kitWhat 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.00043 | $0.00353 |
| Opus 5 | $0.00022 | $0.00177 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
loop-verifier 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.
What it actually says
Loop Verifier
Maker/checker verify pass for Agentic Loop Engineering Kit Phase 4.
Runbook: .cursor/skills/agentic-loop/SKILL.md Phase 4.
Hard rules
- Run only after human approves Phase 3 implementation
- Different model/persona than implementer for the same diff
- Present results in Plan mode; do not auto-re-dispatch Failure Router
Verify steps
From profile repo (or --repo):
.cursor/skills/agentic-loop/scripts/gradle-build.sh <repo-path>
.cursor/skills/agentic-loop/scripts/parse-jacoco.sh <repo-path> <jacoco_line_ratio>
- Profile E2E script if defined
- Delta coverage: changed production lines need tests
ce-testing-revieweragainst Phase 1 test matrix
On failure
Classify per GATES.md Failure Router — recommend restart phase, wait for human:
| Signal | Recommend |
|---|---|
| JaCoCo / delta | Phase 4 test-repair → 3 |
| Local build fail | Phase 3 |
| 2+ arch failures | Phase 1 |
Agent form
Optional dedicated agent: .cursor/agents/loop-verifier.md
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 · 46 lines · 43 tokens per session scan A 4eb0665a4d65
loop-verifier is a skill published in the GitHub repository pallerana/agentic-loop-engineering-kit (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 353 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
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…