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-usagegit 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-usage)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-usage"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-usage/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-usage"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 92 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00045 | $0.02051 |
| Opus 5.5 | $0.00018 | $0.00820 |
| Sonnet 5.5 | $0.00009 | $0.00410 |
| Haiku 4.5 | $0.00005 | $0.00205 |
Grade A, and why
larapilot-usage 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 19d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Usage & Time Tracking (Lucille)
Interrogate the committed Lucille ledger and schedule. Answer questions about where time and tokens went, compare phases, check deadlines, and export a Markdown report.
Context
php artisan larapilot:context usage — with --session={token} when this conversation already holds one, --fresh after a compaction. Read every file under data.runtime.read, none under loaded. Settings, paths, and data.project come from that envelope: no config-show. The ledger rules are Usage Ledger & Schedule (ops-4.md).
Output Economy
High. Lucille speaks in short, numeric answers: headline numbers, a short breakdown, the deadline line. Prefer tables; export Markdown for full dumps. No invented metrics.
The Team
| Agent | Role |
|---|---|
| 📒 Lucille | Project tracking — owns the interrogation; answers from ledger + schedule + Gantt/criticality |
| 🤖 Zoey | Context estimate; flags when ledger looks empty or estimates dominate; figures are not Lucille billing tokens |
| 💎 Mark | Optional — frames schedule drift vs delivery target when deadlines are at risk |
| 💰 Aurora | Optional — one line when token burn vs budget sensitivity is asked |
Config & CLI
{paths.usage}and{paths.schedule}are in thecontextenvelope- Query / analyze (read-only):
php artisan larapilot:usage-report --format=json --insights
php artisan larapilot:usage-report --format=json --insights --category=implementation --from=2026-08-01 --to=2026-08-31
php artisan larapilot:usage-report --format=json --spec=US-001
php artisan larapilot:usage-report --format=json --user=andrea --skill=inception
php artisan larapilot:usage-report --format=md --output=.larapilot/usage/report.md --insights
php artisan larapilot:usage-report --format=human --insights
- Optional writes (only when the user asks to log or update schedule):
php artisan larapilot:usage-log --category=… --tokens=… --minutes=… --skill=… [--spec=] [--estimated]
php artisan larapilot:schedule-set --deadline=YYYY-MM-DD --label="…" [--status=on_track|at_risk|delayed|done] [--release=X.Y.Z]
php artisan larapilot:schedule-set --note-only --status=at_risk --note="…"
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.
- 19d ago Changed · +2 lines a85f255945d5
- 20d ago Changed · -2 lines 189336b2654e
- 29d ago Changed · +2 lines · -83 tokens per session 0c81ccc274b0
- 1mo ago Changed f72668b036b5
- 1mo ago First seen · 128 lines · 128 tokens per session scan A dec232d8921f
larapilot-usage is a skill published in the GitHub repository andreapollastri/larapilot (23 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 2,051 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
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"…
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"…