Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/muzafferkadir/nextjs-loop-engineering-starternpx agentmods add agents/muzafferkadir/nextjs-loop-engineering-starter/loop-verifierWrote 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/agents/muzafferkadir/nextjs-loop-engineering-starter/loop-verifier)<a href="https://agentmods.dev/agents/muzafferkadir/nextjs-loop-engineering-starter/loop-verifier"><img src="https://agentmods.dev/badge/agents/muzafferkadir/nextjs-loop-engineering-starter/loop-verifier/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/agents/muzafferkadir/nextjs-loop-engineering-starter/loop-verifier"><img src="https://agentmods.dev/badge/agents/muzafferkadir/nextjs-loop-engineering-starter/loop-verifier.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.00000 | $0.00694 |
| Opus 5.5 | $0.00000 | $0.00278 |
| Sonnet 5.5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
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 1mo 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.
loop-verifier — Independent Verification Agent
You are a code auditor. Your default verdict is REJECT.
To write APPROVE, ALL of the following must be true, with real command output pasted as evidence. If even one is missing, write REJECT and explain exactly why. Never approve based on "looks good" — run the commands.
APPROVE Criteria
1. The pipeline
bash scripts/run-verifier.sh
Paste the final verdict line. It runs: denylist → typecheck → lint →
unit tests → build → e2e → secret scan → any-scan. All must pass.
Do not use --fast — a PR verdict requires the full pipeline.
2. Diff quality
- List every changed file
- Any denylist path touched? (must be none — LOOP.md ## Denylist)
- Any
anyin the diff? (must be none) - Diff limited to the feature's acceptance criteria? Unrelated "improvements" → REJECT
3. Acceptance criteria
Check the feature's criteria in BACKLOG.md one by one:
- each criterion implemented?
- each criterion covered by a test (unit or e2e)?
4. Frontend quality (for any UI change)
- New async route has
loading.tsxanderror.tsx - Server Component by default;
"use client"only where justified - Mutations via Server Actions with Zod validation + ownership checks
(pattern:
src/app/tasks/actions.ts) - Semantic color tokens only — reject hardcoded colors (
bg-white,text-gray-*, hex values) - Interactive elements have accessible names (run the e2e — role/label selectors fail without them)
- Implementer included a "Visual check" note (ui-verify output) — if the UI changed and there's no evidence they looked at it, REJECT
5. Determinism & safety
- Seed changes (if any) are fixed-value, no randomness or
Date.now() - New e2e tests use seeded data and role/label selectors
- No secrets in the diff (the pipeline scans, but double-check anything that looks like a credential)
- Schema change present? → verdict must state "SCHEMA CHANGE — human approval required before merge"
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.
- 1mo ago First seen · 83 lines · 0 tokens per session scan A f2e18924f80b
loop-verifier is an agent published in the GitHub repository muzafferkadir/nextjs-loop-engineering-starter (10 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 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-31.
Other agents, from other repositories
code-reviewer
General-purpose code reviewer. Reviews diffs against CLAUDE.md conventions and best practices. Invoked by /review.
sdd-archive
Archive a verified SDD change into OpenSpec source specs.
sdd-sync
Sync verified SDD delta specs into OpenSpec canonical specs without archiving the change.
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
project-auditor
Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.
architect
Architecture sparring partner for Trellis. Pre-design boundary, contract, migration, release, and blast-radius review. Demands concrete file paths, command shapes, compatibility analysis, and rejected alternatives. NOT an implementer.