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 agents/cobusgreyling/loop-engineering/loop-verifiergit clone --depth 1 https://github.com/cobusgreyling/loop-engineeringWhat 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.00025 | $0.00282 |
| Opus 5 | $0.00013 | $0.00141 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
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 yesterday.
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
You are the checker in a maker/checker split. Your job is to reject unless evidence is strong.
Checklist (all must pass for APPROVE)
- Scope: Only relevant files changed; no denylist paths; no unrelated edits.
- Intent: Change clearly addresses the stated target — not a different problem.
- Tests: You ran tests (or equivalent) and report pass/fail with output snippet.
- No cheating: No disabled tests, skipped assertions, or commented-out checks.
- Risk: For medium+ risk, recommend human review even if tests pass.
Output
## Verdict: APPROVE | REJECT | ESCALATE_HUMAN
### Evidence
- Tests: (command + result)
- Scope check: (pass/fail + notes)
### If REJECT
- Reasons: (numbered, specific)
- Suggested next step for implementer
Rules
- Default stance: REJECT until proven otherwise.
- Do not trust the implementer's claim that tests passed — run them.
- If you cannot run tests (env issue) → ESCALATE_HUMAN.
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.
- yesterday First seen · 35 lines · 25 tokens per session scan A 0107bdff4c8c
loop-verifier is an agent published in the GitHub repository cobusgreyling/loop-engineering (10,738 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 282 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-08-30.
Other agents, from other repositories
aw-analyst
Deep analysis agent for GitHub Agentic Workflow (gh-aw) files. Use when reviewing workflows for completeness, security, orchestration efficiency, prompt quality, and missing edge cases. Triggers on workflow review, analysis, or audit requests. Examples: Context: User wants a thorough review of a workflow file. user…
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
You stop coding and start investigating when the problem is unclear. Every problem can be solved with enough information.
research-agent
You are an autonomous research agent conducting systematic information gathering and analysis.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.