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/hooksgit 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/hooks)<a href="https://agentmods.dev/instructions/chihebnabil/lovable-boilerplate/hooks"><img src="https://agentmods.dev/badge/instructions/chihebnabil/lovable-boilerplate/hooks.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.00440 | $0.00440 |
| Opus 5 | $0.00220 | $0.00220 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
lovable-boilerplate hooks.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 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.
What it actually says
Custom Hooks Guidelines
HOOK PATTERNS & BEST PRACTICES
Data Fetching Hooks
// PERFECT: Focused data fetching
export const useUsers = () => {
return useQuery({
queryKey: ['users'],
queryFn: () => userService.getAllUsers(),
staleTime: 5 * 60 * 1000, // 5 minutes
})
}
export const useUser = (id: string) => {
return useQuery({
queryKey: ['users', id],
queryFn: () => userService.getUser(id),
enabled: !!id,
})
}
Form Hooks
// PERFECT: Reusable form logic
export const useUserForm = (initialData?: Partial<User>) => {
const form = useForm<UserFormData>({
resolver: zodResolver(userSchema),
defaultValues: initialData || {},
})
const { mutate: saveUser, isPending } = useMutation({
mutationFn: userService.updateUser,
onSuccess: () => toast.success('User saved'),
onError: (error) => toast.error(error.message),
})
return { form, saveUser, isPending }
}
UI State Hooks
// PERFECT: Reusable UI state
export const useDisclosure = (initialState = false) => {
const [isOpen, setIsOpen] = useState(initialState)
return {
isOpen,
open: () => setIsOpen(true),
close: () => setIsOpen(false),
toggle: () => setIsOpen(prev => !prev),
}
}
Hook Naming Convention
- Data:
useUsers,useUser,useProducts - Forms:
useUserForm,useProductForm - UI State:
useDisclosure,useToggle,useLocalStorage - Business Logic:
useAuth,useCart,useNotifications
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 · 67 lines · 440 tokens per session scan A 601dc9b989ff
lovable-boilerplate hooks.instructions.md is an instructions file published in the GitHub repository chihebnabil/lovable-boilerplate (65 stars, last pushed 1mo ago), licensed MIT. It adds 440 tokens to every session, about $0.0022 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.
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.
vibe-stack AGENTS.md
AGENTS.md instructions for vibestackdev/vibe-stack, covering agents.md — ai coding agent instructions, project overview, tech stack, architecture principles and directory structure.
vibe-stack CLAUDE.md
Claude Code instructions for vibestackdev/vibe-stack, covering claude.md — vibe stack architecture rules, for use with claude code (anthropic's agentic cli), project overview, tech stack and critical build commands.
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.