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/chihebnabil/lovable-boilerplate/architecturegit clone --depth 1 https://github.com/chihebnabil/lovable-boilerplateWrote 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/chihebnabil/lovable-boilerplate/architecture)<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/architecture"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/architecture.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.02728 | $0.02728 |
| Opus 5 | $0.01364 | $0.01364 |
| Sonnet 5 | $0.00546 | $0.00546 |
| Haiku 4.5 | $0.00273 | $0.00273 |
Grade A, and why
lovable-boilerplate architecture.instructions.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 5d 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Architecture & Reusability Guidelines
CRITICAL ARCHITECTURE RULES
NEVER CREATE:
- Components over 300 lines
- Duplicate logic across components
- Inline API calls in UI components
- Mixed concerns (UI + business logic + API)
- Copy-pasted code blocks
ALWAYS CREATE:
- Single-responsibility components (20-100 lines)
- Custom hooks for reusable logic
- Service layer for API calls
- Shared types in
lib/types.ts - Composition patterns from smaller components
Component Composition Over Monoliths
NEVER create large, monolithic components that handle multiple concerns: Avoid: Single components or page that exceed 300 lines or handle multiple responsibilities Avoid: Pages that contain all logic inline instead of using smaller components Avoid: Components that mix UI rendering, business logic, and API calls
ALWAYS break down complex functionality into smaller, reusable pieces: Create: Focused components with single responsibilities (20-100 lines) Create: Composition patterns using multiple small components Create: Custom hooks for reusable logic extraction Create: Separate layers for data fetching, business logic, and presentation
Component Organization Strategy
1. Feature-Based Organization
// Wrong: Everything in one file
const Dashboard = () => {
// 300+ lines of mixed logic
return <div>{/* massive JSX */}</div>
}
// ✅ Correct: Composed from focused components
const Dashboard = () => (
<DashboardLayout>
<DashboardHeader />
<DashboardStats />
<DashboardCharts />
<DashboardActivity />
</DashboardLayout>
)
2. Reusable Component Patterns
// ✅ Base components for consistent UI patterns
const Card = ({ children, className, ...props }) => (
<div className={cn("rounded-lg border bg-card", className)} {...props}>
{children}
</div>
)
// ✅ Composite components for complex patterns
const StatsCard = ({ title, value, change, icon: Icon }) => (
<Card className="p-6">
<div className="flex items-center justify-between">
<div>
<p className="text-sm text-muted-foreground">{title}</p>
<p className="text-2xl font-bold">{value}</p>
<p className="text-sm text-green-600">{change}</p>
</div>
<Icon className="h-8 w-8 text-muted-foreground" />
</div>
</Card>
)
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.
- 5d ago First seen · 381 lines · 2,728 tokens per session scan A 1d9111e00b18
lovable-boilerplate architecture.instructions.md is an instructions file published in the GitHub repository chihebnabil/lovable-boilerplate (65 stars, last pushed 1mo ago), licensed MIT. It adds 2,728 tokens to every session, about $0.0136 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
oh-my-copilot AGENTS.md
AGENTS.md instructions for RobinNorberg/oh-my-copilot, covering oh-my-copilot - intelligent multi-agent orchestration, working agreements, setup and review guidelines.
claude-task-master CLAUDE.md
Claude Code instructions for eyaltoledano/claude-task-master, covering claude code instructions, task master ai instructions, test guidelines, test file placement and synchronous tests.
oh-my-copilot CLAUDE.md
Claude Code instructions for RobinNorberg/oh-my-copilot, covering oh-my-copilot - intelligent multi-agent orchestration and setup.
agentconfig.org AGENTS.md
Instructions for agentconfig/agentconfig.org, covering agent instructions for agentconfig.org, project overview, target audience, site structure and tech stack.
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.