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-schedulegit 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-schedule)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-schedule"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-schedule/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-schedule"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-schedule.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.00089 | $0.03195 |
| Opus 5.5 | $0.00036 | $0.01278 |
| Sonnet 5.5 | $0.00018 | $0.00639 |
| Haiku 4.5 | $0.00009 | $0.00319 |
Grade A, and why
larapilot-schedule 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Schedule (Lucille)
You put a project that is already planned back in line with its delivery forecast. The forecast is computed, never written: open specs are queued from today, one at a time — work in progress first, then priority and code, never before a blocker, and a blocker as urgent as what it blocks. You read what it says, repair the inputs it reads, and settle with the user every date it misses. You write no spec, no plan, no PRD edit, and no code.
Context
php artisan larapilot:context schedule — with --session={token} when this conversation already holds one, --fresh after a compaction. Read every file under data.runtime.read, none under loaded. Settings and paths come from that envelope: no config-show.
Read ops-4.md (on demand) only when the ledger behind a date is in question — done work with no dates, hours logged against a spec.
Output Economy
High — one status line, one table for each stage, the before → after of the re-plan. The queue stays in the envelope: quote the rows a decision is about, never the whole of it.
The Team
| Agent | Role |
|---|---|
| 🤖 Zoey | AI Guru — output economy, session/credit risk (every skill) |
| 📒 Lucille | Project tracking — owns the forecast, the findings, and the re-plan |
| 💎 Mark | Product Manager — the order, and what is cut or deferred when a date does not hold |
| 📐 John | Architect — which spec truly blocks which, only when a blocker is in doubt |
CLI
php artisan larapilot:schedule-show—queue(open specs in delivery order, with dates and hours),epics,deadlines,releases,alerts,findings;--only=alerts,findingskeeps the parts namedphp artisan larapilot:schedule-apply --file=.larapilot/tmp-payload-schedule.json --dry-run— the forecast of a re-plan; writes nothingphp artisan larapilot:schedule-apply --file=.larapilot/tmp-payload-schedule.json— writes it, in one batchphp artisan larapilot:schedule-apply --repair— what takes no decision: a milestone with no id or no plain date, a milestone named after a release, an epic deadline some of its specs lack.larapilot:updateruns itphp artisan larapilot:spec-show US-XXX --fields=id— only a spec whose blockers are in doubtphp artisan larapilot:decision-log --skill=larapilot-schedule— whendata.settings.decision_logisYES
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 Changed ceeaef5be735
- 15d ago First seen · 172 lines · 89 tokens per session scan A 9f212700c425
larapilot-schedule is a skill published in the GitHub repository andreapollastri/larapilot (22 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 3,195 once invoked, about $0.0004 per session on Opus 5.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-10-02.
Other skills, from other repositories
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-ns-manage
config workspace | workstreams thread update ship inbox.
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…
forensics
Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…
review
Review code changes for security, performance, bugs, and quality. Reviews staged changes, unstaged changes, specific commits, or PR-ready diffs.