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/pagesgit 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/pages)<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/pages"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/pages.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.00515 | $0.00515 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
lovable-boilerplate pages.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.
What it actually says
Page Component Guidelines
PAGE ARCHITECTURE RULES
Pages are COMPOSITION ONLY
Pages should be thin orchestration layers that compose smaller components:
// PERFECT: Page as composition layer (10-30 lines max)
const DashboardPage = () => {
return (
<PageLayout>
<DashboardHeader />
<DashboardMetrics />
<div className="grid grid-cols-1 lg:grid-cols-2 gap-6">
<DashboardCharts />
<DashboardActivity />
</div>
</PageLayout>
)
}
// NEVER: Business logic in pages
const BadDashboardPage = () => {
const [users, setUsers] = useState([])
const [loading, setLoading] = useState(true)
useEffect(() => {
// 50+ lines of data fetching logic
}, [])
// 200+ lines of rendering logic
return <div>{/* massive JSX */}</div>
}
Page Organization Rules
- Import dependencies (max 5-8 imports)
- Call custom hooks for data/state (1-3 hooks max)
- Return JSX composition (10-20 lines max)
- No business logic - extract to hooks or services
- No inline handlers - extract to components or hooks
Data Loading Pattern
```tsx
// PERFECT: Data loading in custom hooks
const UserProfilePage = () => {
const { user, isLoading, error } = useUser()
if (isLoading) return <LoadingSpinner />
if (error) return <ErrorMessage error={error} />
return (
<PageLayout>
<UserHeader user={user} />
<UserDetails user={user} />
<UserActivity user={user} />
</PageLayout>
)
}
### Page File Structure
src/pages/ ├── Index.tsx # Landing page ├── Dashboard.tsx # Main dashboard ├── Users/ │ ├── UsersPage.tsx # Users list page │ └── UserDetail.tsx # Single user page ├── Settings/ │ ├── SettingsPage.tsx │ └── ProfilePage.tsx └── NotFound.tsx # 404 page
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 · 81 lines · 515 tokens per session scan A 4e33adc6597f
lovable-boilerplate pages.instructions.md is an instructions file published in the GitHub repository chihebnabil/lovable-boilerplate (65 stars, last pushed 1mo ago), licensed MIT. It adds 515 tokens to every session, about $0.0026 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
ai-website-cloner-template copilot-instructions.md
Instructions for JCodesMore/ai-website-cloner-template, covering this is not the next.js you know, website reverse-engineer template, what this is, tech stack and commands.
packmind packmind-frontend-data-flow.instructions.md
Instructions for PackmindHub/packmind: This standard defines the recommended data flow pattern for frontend routes in the Packmind codebase using React Router v7 in framework mode with TanStack Query for data management. It ensures consist... .
packmind packmind-frontend-navigation-with-react-router.instructions.md
Instructions for PackmindHub/packmind: This codebase uses React Router v7 with organization and space scoping in URLs (e.g., /org/{orgSlug}/space/{spaceSlug}/recipes). To maintain consistency, improve maintainability, and simplify navigati... .
build-applications-w-copilot-agent-mode octofit_tracker_setup_project.instructions.md
Instructions for skills/build-applications-w-copilot-agent-mode, covering octofit tracker multi-tier application setup guidelines, application goals, command execution rules, forwarded ports and project structure.
build-applications-w-copilot-agent-mode octofit_tracker_react_frontend.instructions.md
Instructions for skills/build-applications-w-copilot-agent-mode, covering octofit tracker react presentation tier guidelines and images.
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.