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 romiluz13/auto-pi --skill setup-maintenancegit clone --depth 1 https://github.com/romiluz13/auto-piWrote 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/romiluz13/auto-pi/setup-maintenance)<a href="https://agentmods.dev/skills/romiluz13/auto-pi/setup-maintenance"><img src="https://agentmods.dev/badge/skills/romiluz13/auto-pi/setup-maintenance/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/romiluz13/auto-pi/setup-maintenance"><img src="https://agentmods.dev/badge/skills/romiluz13/auto-pi/setup-maintenance.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.00062 | $0.01222 |
| Opus 5.5 | $0.00025 | $0.00489 |
| Sonnet 5.5 | $0.00012 | $0.00244 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
setup-maintenance 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Maintenance
A setup that doesn't degrade is a setup with a maintenance discipline. This skill defines the cadence + the two loops: maintenance (prevent drift) and improvement (find new leverage). The one-command runner is /setup-audit.
The two loops
Maintenance loop — prevent drift. Versions fall behind, new packages conflict, skills bloat, disk grows, AGENTS.md goes stale, extensions develop latent bugs. Without a check, you discover this when something breaks at the worst time.
Improvement loop — find new leverage. The Pi ecosystem ships new packages/features weekly. Other setups (cc10x, Archon, spences10, tomsej/pi-ext) invent techniques worth stealing. Without a scan, you plateau. This is the loop that turned a good setup into a best-contender.
The cadence
| When | What | How |
|---|---|---|
| Monthly | Full audit (both loops) | /setup-audit — fans out 6 subagents, writes a report |
| On-add (new package/extension) | Harmony re-audit | Read the new package's tools/commands/hooks/storage; check for collisions against existing packages + extensions (enumerate dynamically from settings.json + extensions dir). Reject if it duplicates an existing axis. |
| Before-publish (pushing my-pi) | Full audit + sync | /setup-audit → fix criticals → sync settings/extensions/skills to ~/Dev/my-pi → commit + push |
| On-extend (new skill) | Coach coverage check | After adding a skill, grep coach.ts — does any intent route to it? If not, add a detector or it's unreachable via Coach. |
The /setup-audit runner
/setup-audit dispatches 6 parallel read-only subagents:
- Version freshness — installed vs latest for Pi core + all npm packages. Flags drift + deprecation.
- Harmony re-audit — tool/command/hook/storage collisions across all packages + extensions. File:line evidence.
- Coach coverage scan — lists EVERY command + skill, flags which Coach never routes to. Each gap = leverage the setup has but doesn't surface. This is the highest-value axis — it's how we found the wayfinder gap.
- Disk growth — sessions, hermes DB, workflows, context sidecar. Flags unbounded stores > 100MB.
- AGENTS.md accuracy — line count (must be < 200) + does it match reality.
- Ecosystem scan — new Pi packages + public setups worth stealing from. Conflict-assessed.
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.
- 1mo ago First seen · 71 lines · 62 tokens per session scan A fef351417f45
setup-maintenance is a skill published in the GitHub repository romiluz13/auto-pi (10 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,222 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
configure-pi-starship
Configure @narumitw/pi-starship and answer questions about its pi-starship.toml settings. Use when the user asks to create, edit, repair, migrate, or understand pi-starship.toml, or asks which pi-starship module, variable, option, style, palette, preset, or runtime behavior to use. Do not use for generic TOML, shell…
configure-pi-sync
Explain @narumitw/pi-sync settings and guide safe setup through its existing manager. Use when the user asks how to configure pi-sync.json, choose Git, WebDAV, R2, or S3 storage, select synced content, understand automatic controls, or recover unsupported settings. This skill provides guidance only, not settings edits…
fabric-foreman
Starts a bounded Jev foreman above Main's coding work, assessing progress, drift, blockers, and verification per turn or at agent settlement with deterministic intervention policy.
write-swift
How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know…
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
apple-design
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…