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 instructions/lovablelabs/mcp/claude-mdgit 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/instructions/lovablelabs/mcp/claude-md)<a href="https://agentmods.dev/instructions/lovablelabs/mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/lovablelabs/mcp/claude-md.svg" alt="Measured on agentmods" 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 | $0.00976 | $0.00976 |
| Opus 5 | $0.00488 | $0.00488 |
| Sonnet 5 | $0.00195 | $0.00195 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
mcp CLAUDE.md 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lovable for Claude Code
Build, iterate on, deploy, and manage Lovable apps without leaving Claude Code.
The official Claude Code plugin for Lovable, the AI-powered full-stack app builder. It bundles the official Lovable MCP server — pre-wired, with automatic OAuth — plus focused commands for the workflows developers reach for most.
Why use it
Lovable builds and hosts full-stack apps; Claude Code is your local agent. This plugin connects the two so you can drive Lovable from your terminal: describe an app and ship it, request a change and review the diff, or provision and query a database — all in natural language, with credit- and publish-safety prompts built in.
What's included
| Command | What it does | Lovable tools used |
|---|---|---|
/lovable:build <description> |
Create a new project from a prompt, follow the build, and optionally deploy to a live URL | list_workspaces, create_project, send_message, get_project, deploy_project |
/lovable:iterate <project> — <change> |
Send a change request to a project's agent (plan-first for big changes) and review the unified diff | list_projects, send_message, get_message, get_diff, list_edits |
/lovable:db <project> [SQL] |
Check/enable a Lovable Cloud Postgres database and run SQL with confirmation | get_database_status, enable_database, query_database, get_database_connection_info |
Every other Lovable MCP tool (analytics, knowledge/governance, connectors, file inspection, templates, …) is also available to Claude Code once the plugin is installed — the commands above just package the common flows.
Requirements
- Claude Code (a version with plugin + remote-MCP support)
- A Lovable account
Install
/plugin marketplace add lovablelabs/mcp
/plugin install lovable@lovable
Restart Claude Code (or reload plugins). The first time a Lovable tool runs, Claude Code opens a browser window to sign in to Lovable.
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.
- 4d ago First seen · 78 lines · 976 tokens per session scan A 2d31b6567a92
mcp CLAUDE.md is an instructions file published in the GitHub repository lovablelabs/mcp (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 976 tokens to every session, about $0.0049 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 instructions, from other repositories
aicode-toolkit CLAUDE.md
Claude Code instructions for AgiFlow/aicode-toolkit, covering claude.md, project overview, coding workflow (important), 1. creating new applications or features and 2. before editing files.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Claude Code instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.