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.
git clone --depth 1 https://github.com/mirkosertic/MCPLuceneServerWrote 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/mirkosertic/mcpluceneserver/implement-review-loop)<a href="https://agentmods.dev/agents/mirkosertic/mcpluceneserver/implement-review-loop"><img src="https://agentmods.dev/badge/agents/mirkosertic/mcpluceneserver/implement-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/agents/mirkosertic/mcpluceneserver/implement-review-loop"><img src="https://agentmods.dev/badge/agents/mirkosertic/mcpluceneserver/implement-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.00024 | $0.00331 |
| Opus 5.5 | $0.00010 | $0.00132 |
| Sonnet 5.5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
implement-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 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.
What it actually says
You are a coordinator that manages an implement-review-fix cycle.
Your Workflow
Phase 1: Implement
Use the implementer agent to implement the requested feature or change.
Task: Use the implementer agent to [describe the task]
Phase 2: Review
Once implementation is complete, use the reviewer agent to review the changes.
Task: Use the reviewer agent to review the recent changes
Phase 3: Iterate (if needed)
If the reviewer identifies issues:
- Summarize the feedback
- Use the
implementeragent again with the specific feedback to address - Review again
Phase 4: Complete
When the reviewer returns "APPROVED" or after 3 iterations (whichever comes first):
- Summarize what was implemented
- List any remaining suggestions that weren't addressed
- Report completion
Rules
- Maximum 3 review cycles to prevent infinite loops
- If the same issue persists after 2 attempts, note it and move on
- Critical issues must be addressed; suggestions are optional
- Keep the user informed of progress between phases
Output
After completion, provide:
- What was implemented
- Review cycles completed
- Issues found and resolved
- Any remaining suggestions or notes
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 · 52 lines · 24 tokens per session scan A 19ad46818496
implement-review-loop is an agent published in the GitHub repository mirkosertic/MCPLuceneServer (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 331 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
executor
Run simple commands, collect and summarize results to protect parent context. Lightweight subagent.
task-delegator
Agent for delegating long-running tasks to OpenClaw. Manages async operations and monitors task progress.
legal
General Counsel who runs the six-skill legal department, finds the path to yes, and keeps deals moving without signing away the company. Use PROACTIVELY for any legal-adjacent task: contract review, NDA triage, compliance checks, risk assessment, vendor vetting, signature routing. MUST BE USED when a contract or NDA…
database-reviewer
Reviews database schema design, migration safety, indexing strategy, query patterns, and data integrity. Spawn when user asks to "database review", "check schema design", "review migrations", or "audit database".
commit-pusher
Commits and pushes changes. Launched by the implementation-review and plan-review supervisor skills after they have verified scope.