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/build)<a href="https://agentmods.dev/commands/lovablelabs/mcp/build"><img src="https://agentmods.dev/badge/commands/lovablelabs/mcp/build/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/build"><img src="https://agentmods.dev/badge/commands/lovablelabs/mcp/build.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.00013 | $0.00221 |
| Opus 5.5 | $0.00005 | $0.00088 |
| Sonnet 5.5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
build 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
Build a new Lovable app described as: $ARGUMENTS
Use the Lovable MCP tools to do this end to end:
- Call
list_workspacesto find the target workspace. If the user belongs to more than one, ask which to use. - Confirm with the user before spending credits. Then call
create_projectin that workspace with an initial build prompt derived from the description above. - Follow the agent's progress with
send_message/get_messageuntil the initial build completes. - Call
get_projectand share the editor URL and preview URL with the user. - Ask whether to publish. If yes, call
deploy_projectand return the live URL.
Notes:
create_projectandsend_messageconsume Lovable build credits — always confirm first.deploy_projectpublishes a publicly reachable URL on Free/Pro plans.
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 · 19 lines · 13 tokens per session scan A af9566700c86
build is a command published in the GitHub repository lovablelabs/mcp (7 stars, last pushed 22d ago), licensed Apache-2.0. It adds 13 tokens to every session and 221 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.
start
Start an OBTO session — verify identity, resolve the working domain, and set the working context.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
connect-vybe
Connect and authenticate the Vybe Solana MCP server over OAuth.
ingest-dev
Ingest a URL, directory, or file into your knowledge base. remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.