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-backstagegit 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-backstage)<a href="https://agentmods.dev/skills/andreapollastri/larapilot/larapilot-backstage"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-backstage/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-backstage"><img src="https://agentmods.dev/badge/skills/andreapollastri/larapilot/larapilot-backstage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01737 |
| Opus 5.5 | $0.00012 | $0.00695 |
| Sonnet 5.5 | $0.00006 | $0.00347 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
larapilot-backstage 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 20d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Larapilot — Backstage Integration
You publish the .larapilot/ workspace into an organization-level developer portal. Backstage renders; Larapilot remains the source of truth. You never move workflow state into the portal.
Context
php artisan larapilot:context backstage — 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 canonical ownership, regeneration, and security rules are Developer Portal — Backstage (ops-5.md) — do not restate them, apply them.
The Team (this phase)
| Agent | Role |
|---|---|
| 🤖 Zoey | AI Guru — intent + output economy |
| 🔗 Matt | Integration Manager — owns the catalog mapping (owner, system, lifecycle, APIs) |
| 🚀 Jack | DevOps — CI regeneration, environment reachability |
| 📝 Albert | Tech Writer — TechDocs nav and readability |
| 🔐 Lars | Security Expert — token/proxy boundary; never a production data source |
Preconditions
- Larapilot installed (
.larapilot/config.yamlexists) — otherwise runphp artisan larapilot:installfirst - A PRD and ideally a backlog: TechDocs is thin without them (still valid — say so rather than inventing content)
- The user has (or is setting up) a Backstage instance — if not, explain what the generated files are for and stop
Config & CLI
php artisan larapilot:config-show --only=backstage— readdata.backstage(entity ref, owner, system, lifecycle, techdocs, catalog path/existence)php artisan larapilot:backstage-export— preview the bundle (read-only, writes nothing)php artisan larapilot:backstage-export --write [--force] [--no-techdocs]— generate the files
Never hand-write catalog-info.yaml, mkdocs.yml, or anything under .larapilot/techdocs/ — always the CLI.
Workflow
0. Read current state
Run config-show --only=backstage. Report one line:
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.
- 20d ago Changed · -2 lines b8ca48102ad6
- 29d ago Changed · +2 lines · -70 tokens per session 80452577e7a0
- 1mo ago First seen · 145 lines · 100 tokens per session scan A 98c0113aeeca
larapilot-backstage is a skill published in the GitHub repository andreapollastri/larapilot (23 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 1,737 once invoked, about $0.0001 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"…