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 skills add andreapollastri/larapilot --skill larapilot-plangit 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-plan)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-plan"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-plan.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.00077 | $0.03059 |
| Opus 5 | $0.00039 | $0.01529 |
| Sonnet 5 | $0.00015 | $0.00612 |
| Haiku 4.5 | $0.00008 | $0.00306 |
Grade A, and why
larapilot-plan 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 2d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Spec Planning
Produce a detailed implementation plan for one spec and persist it via the CLI.
Shared Runtime
Read .larapilot/shared-runtime.md (core — Project Settings, Sub-agents), then .larapilot/runtime-delivery.md (architecture, Git/TASK-00, factories/seeders, testing gates, scaffolding defaults, vendor policy, docs). When the spec has UI, also read .larapilot/runtime-ux.md (mobile-first, a11y, brand, SEO).
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.
Read .larapilot/task-templates.md — copy task body structures gated by data.settings.
Output Economy
Split — see larapilot-plan in the shared-runtime table. Team brief: 1–3 sentences per agent. Chat between stages: status and blockers only. plan_body and task bodies stay detailed execution contracts.
The Team
🤖 Zoey · 📒 Lucille · 🔎 Tom · 📐 John · 🗄️ Mike · 💡 Sebastian · 🔗 Matt · 🌍 Emily · 💰 Aurora · ⚖️ Violet · 📈 Emma · 💬 Lauren · 🎨 Elise · ✨ Joe · 📱 Ricky · 📝 Albert · ✍️ Marika · 👾 Andrew · ⌨️ Sarah · 🔄 Sabrine · 🔧 Alex · 🧪 Anne — roles in the shared-runtime roster. Mike owns data/schema tasks; Sarah owns Git mechanics (conflicts/rebase), CLI, forge automation, CI pipeline scripts, and Linux/server scripting whenever those surfaces appear (partner Jack on gates/deploy).
Config & CLI
php artisan larapilot:config-show— readdata.settingsand scale Git/Test Strategy accordinglyphp artisan larapilot:spec-show {code}ORphp artisan larapilot:spec-next --status=TODOphp artisan larapilot:validate-plan {code} --file=...php artisan larapilot:spec-plan {code} --file=...
Workflow
Stage 0 — Select spec
- With code argument →
spec-show - Without argument →
spec-next - Free-text descriptions → route to
larapilot-specfirst
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.
- 2d ago Changed · +2 lines 5e4072dea674
- 7d ago First seen · 160 lines · 77 tokens per session scan A 322654f0d7c6
larapilot-plan is a skill published in the GitHub repository andreapollastri/larapilot (19 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 3,059 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
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
frontend-craft-director
A self-contained frontend design, redesign, audit, implementation, anti-AI-slop, and rendered visual-QA skill for use directly inside a ChatGPT conversation or through a local MCP-accessible project.
cat:learn-from-mistakes
Analyze mistakes with conversation length as potential cause (CAT-specific).
skill-builder
Use BEFORE creating or updating any skill OR command - decomposes goal into forward steps via backward reasoning.
compare-docs
Compare two documents semantically with relationship preservation to identify content and structural differences.
cat:spawn-subagent
Launch subagent with task context in isolated worktree with token tracking.