Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/andreapollastri/larapilot/larapilot-frontend-companion)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-frontend-companion"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-frontend-companion/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/skills/andreapollastri/larapilot/larapilot-frontend-companion"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-frontend-companion.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.00081 | $0.00708 |
| Opus 5 | $0.00041 | $0.00354 |
| Sonnet 5 | $0.00016 | $0.00142 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
larapilot-frontend-companion 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 11d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — External frontend repo
When Frontend Topology is API + external frontend, everything runs from the Laravel workspace. The FE repo is a linked write target — not a second Larapilot cockpit.
How it works
- Laravel owns PRD, backlog, plans, mockups, workflow state.
frontend.repo_pathin.larapilot/config.yamlpoints to the absolute FE directory.larapilot-plan/larapilot-implementwrite UI code there via tasks markedrepo: frontend.
The FE repo holds application code only — no mirrored PRD, no Larapilot workflow.
When to use
- Setting up or verifying split-repo delivery from Laravel
- User provides or changes the absolute FE repo path
- Before first plan on an existing FE codebase (
frontend-scan)
Shared Runtime
Read .larapilot/shared-runtime.md (core) and .larapilot/runtime-discovery.md → Frontend Topology.
The Team
| Agent | Role |
|---|---|
| 🤖 Zoey | AI Guru — output economy |
| ✨ Joe | Frontend Expert — stack + existing code from scan |
| 📐 John | Architect — API boundaries |
| 🔗 Matt | Integration — auth/CORS/OpenAPI |
| 🎨 Elise | UX — mockups stay in Laravel .larapilot/mockups/ |
Workflow
1. Link the FE repo (once)
If config-show → data.frontend.configured is false, ask for the absolute path (e.g. /Users/dev/acme-web).
php artisan larapilot:frontend-set --path=/absolute/path/to/fe-repo --stack=React
Record the same path in the PRD → External frontend repo.
2. Scan existing code (before plan / evolutive)
php artisan larapilot:frontend-scan
Summarize stack, tooling, directories, entrypoints. Joe uses this so specs start from code already present.
3. Deliver from Laravel
/larapilot-spec → /larapilot-plan → /larapilot-implement — all from this workspace.
- Backend tasks → Laravel (
repo: backendor default) - UI tasks →
repo: frontend, paths underdata.frontend.repo_path - FE git:
git -C {repo_path} …· FE tests:npm test/ vitest from FE root
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.
- 11d ago First seen · 75 lines · 81 tokens per session scan A b47467c1b61f
larapilot-frontend-companion is a skill published in the GitHub repository andreapollastri/larapilot (19 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 708 once invoked, about $0.0004 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 skills, from other repositories
trigger-realtime-and-frontend
Trigger.dev client/frontend surface: subscribe to runs in realtime (runs.subscribeToRun and the @trigger.dev/react-hooks hook useRealtimeRun), consume metadata and AI/text streams in React (useRealtimeStream), trigger tasks from the browser (useTaskTrigger, useRealtimeTaskTrigger), and mint scoped frontend credentials…
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
tanstack-start
Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 +…
multi-method-image-generation
An image-making workflow that tries multiple available sources and methods, including image-generation services, HTML and CSS rendering, existing photos, and website assets. It creates several candidates so they can be compared and recommended.
webapp-building
Build or modify production-oriented web applications by following the repository architecture and validating real user flows.