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/lovablelabs/mcpWrote 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/commands/lovablelabs/mcp/iterate)<a href="https://agentmods.dev/commands/lovablelabs/mcp/iterate"><img src="https://agentmods.dev/badge/commands/lovablelabs/mcp/iterate/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/commands/lovablelabs/mcp/iterate"><img src="https://agentmods.dev/badge/commands/lovablelabs/mcp/iterate.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.00014 | $0.00185 |
| Opus 5.5 | $0.00006 | $0.00074 |
| Sonnet 5.5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
iterate 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
Iterate on a Lovable project. Request: $ARGUMENTS
- Resolve the target project. If the user gave a name rather than an ID, call
list_projectsand confirm theproject_idwith them. - For a non-trivial change, call
send_messagewithplan_modefirst so the user can approve the plan before code is written. This consumes build credits — confirm first. - When the message completes (poll
get_messageif needed), callget_diffwith the returnedmessage_idand show the user the unified diff. - Summarize what changed. Offer to iterate further, view history with
list_edits, or publish withdeploy_project.
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 · 12 lines · 14 tokens per session scan A ba59dbc57a37
iterate is a command published in the GitHub repository lovablelabs/mcp (7 stars, last pushed 22d ago), licensed Apache-2.0. It adds 14 tokens to every session and 185 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-30.
Other commands, from other repositories
edit-with-pattern
Edit a file using toolkit design-pattern guidance and review the result.
is-not-duplicated
please investigate the codebase based on your changes - do we have code duplication? After analysis, write updates to DUPLICATIONREPORT.md with the results. Keep in mind that other agents could keep their records, so you need to check the document first, decided to update or add new information.
review
Comprehensive code review for blz changes.
review
Review the current plan with peer LLMs via inspectrum.
implement
Multi-agent advisory squad workflow for implementing code changes: classify → score risk → select agents → planner → Gate 1 (plan approval) → advisory squad → Gate 2 (Blocker halt) → implementer → consolidator → verdict. Auto-detects depth (quick/normal/deep) from risk + file count; pass --quick or --deep to override.…
inventory
Codebase inventory skill — scans the repo for a named pattern (inline SQL, fetch calls, feature flags, debug leftovers, deprecated APIs, etc.) and emits a structured Markdown inventory cross-referenced with framework metadata (routes, handlers). Language-agnostic and pack-driven — the engine matches whatever a YAML…