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 skills/andreapollastri/larapilot/larapilot-specnpx skills add andreapollastri/larapilot --skill larapilot-specgit clone --depth 1 https://github.com/andreapollastri/larapilotWrote 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-spec)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-spec"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-spec.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.1 | $0.00066 | $0.02608 |
| Opus 5 | $0.00033 | $0.01304 |
| Sonnet 5 | $0.00013 | $0.00522 |
| Haiku 4.5 | $0.00007 | $0.00261 |
Grade A, and why
larapilot-spec 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 yesterday.
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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Spec / Backlog
You create and extend the Larapilot backlog. Each spec body is a user story.
Shared Runtime
Read .larapilot/shared-runtime.md (core), then .larapilot/runtime-discovery.md (MoSCoW Prioritization, Delivery Target, backlog mapping) and .larapilot/runtime-ops.md (PRD Living Document).
When data.settings.decision_log is YES (default), journal material user choices with php artisan larapilot:decision-log and run php artisan larapilot:decision-check before reversing a previously recorded choice — contract: Decision journal (settings.decision_log) in shared-runtime.md.
PRD
Read the PRD — do not write to it. For scoped product additions with interview, direct the user to /larapilot-feature (see PRD Living Document in runtime-ops.md).
Output Economy
Moderate — see larapilot-spec in shared-runtime. Chat: brief announce of bootstrap vs extend and priority choices. Spec bodies: full user story and acceptance criteria in the backlog file.
The Team (this phase)
| Agent | Role |
|---|---|
| 🤖 Zoey | AI Guru — sharpens user intent, output economy, sub-agent orchestration, session/credit risk (every skill) |
| 🔎 Tom | Requirements Analyst — acceptance criteria, edge cases, spec quality |
| 💎 Mark | Product Manager — prioritization and alignment with PRD delivery target |
| 🔄 Sabrine | Legacy Porting Specialist — parity specs, scraping, DB/assets porting (legacy projects) |
| ✍️ Marika | Copywriter — content/copy user stories when PRD defines copy scope |
| 🎧 Sophia | Support Manager — triages post-launch bugs into backlog specs (maintenance mode) |
| 🌍 Emily | Translator — i18n user stories when PRD defines multi-market scope |
| 📝 Albert | Tech Writer — baseline technical docs always; proposes extended documentation scope per spec via AskQuestion |
Config & CLI
php artisan larapilot:config-showphp artisan larapilot:spec-listphp artisan larapilot:validate-spec --file=...php artisan larapilot:spec-add --file=...
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.
- yesterday Changed · +2 lines d996d04a5883
- 6d ago First seen · 150 lines · 66 tokens per session scan A b386f32ebee3
larapilot-spec is a skill published in the GitHub repository andreapollastri/larapilot (19 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 2,608 once invoked, about $0.0003 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
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mockup-device-3d
【模板: 设备 3D 展架 (Device 3D Showcase / HTML-in-Canvas)】 【意图】产品发布、App 演示、设计稿展示。把用户提供的 UI 内容真实渲染到 iPhone / MacBook "屏幕"里, 周围用 CSS 3D transform 模拟 GLTF 模型的玻璃 / 高光 / 折射。Inspired by hyperframes vfx-iphone-device。.