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 narumiruna/pi-extensions --skill configuring-pi-starshipgit clone --depth 1 https://github.com/narumiruna/pi-extensionsWrote 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/narumiruna/pi-extensions/configuring-pi-starship)<a href="https://agentmods.dev/skills/narumiruna/pi-extensions/configuring-pi-starship"><img src="https://agentmods.dev/badge/skills/narumiruna/pi-extensions/configuring-pi-starship/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/narumiruna/pi-extensions/configuring-pi-starship"><img src="https://agentmods.dev/badge/skills/narumiruna/pi-extensions/configuring-pi-starship.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.00098 | $0.01237 |
| Opus 5 | $0.00049 | $0.00619 |
| Sonnet 5 | $0.00020 | $0.00247 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
configuring-pi-starship 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring pi-starship
Answer pi-starship configuration questions or make the requested pi-starship.toml change.
Choose the task path
For a configuration question, load only the smallest relevant reference and answer with the exact supported names, values, defaults, and behavior.
Do not read or modify the user's settings file for a question that the references can answer directly.
For a configuration edit, inspect the existing document and follow the editing and validation workflow below.
Treat the bundled references and implementation as authoritative instead of assuming compatibility with shell Starship.
If the references do not answer a question, inspect the bundled source relative to this skill.
Use ../../src/config.ts for parsing, defaults, validation, and persistence behavior.
Use ../../src/modules/catalog.ts, ../../src/modules/types.ts, and the relevant ../../src/modules/*.ts file for module variables, options, defaults, and runtime values.
Use ../../src/presets/ for the exact bundled preset documents.
State clearly when an answer comes from implementation detail rather than a documented public configuration surface.
Load configuration references
Read configuration and format for settings location and persistence, presets, complete examples, root and module formats, styles, palettes, and display thresholds.
Read the complete module catalog for exact module names, format variables, default formats, symbols, enabled state, style fields, display defaults, option types, ranges, and enum values.
For one module, search that catalog for its exact ### \module_name`` heading and read only through the next module heading.
Read module behavior for output semantics, detection defaults, aliases, truncation, and module-specific behavior.
Read runtime and security before enabling or explaining network, command-backed, development, cloud, deployment, host, user, or width-sensitive modules, and when checking limitations.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 114 lines · 98 tokens per session scan A a53fb645050e
configuring-pi-starship is a skill published in the GitHub repository narumiruna/pi-extensions (539 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 1,237 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
pi-tui-design
Create distinctive, crafted TUI components for pi using @mariozechner/pi-tui and @mariozechner/pi-coding-agent. Use when building interactive terminal UIs — custom components, overlays, dialogs, dashboards, widgets, data visualizations, animated elements, game-like interfaces, or any visual TUI work inside pi…
session-search
Search and verify Joel's Pi, Claude, Codex, Cursor, Grok, and OpenCode session history. Use when asked to recover prior context, find exact transcript evidence, inspect session receipts, continue old work, or verify capture health. Prefer flowing recall before raw transcript search when the question is about prior…
linear-tracker
Resolve project-local issue tracker routing and publish Linear issues safely. Use before creating Linear issues, PRDs, phase breakdown issues, or when deciding whether Linear/GitHub/local docs is the configured tracker. Enforces capability ≠ routing: Linear requires project-local policy, team association, auth, and…
shortlink-qr
Create joel.dev shortlinks and QR assets. Use when Joel asks for a QR code, stage/demo shortlink, joel.dev redirect, link label that looks good in phone camera UI, or a copyable QR asset.
session-capture
Historical pointer for the retired Codex-to-Central capture plugin. Use only to inspect legacy state during migration; current capture belongs to the joelclaw flowing-memory host adapter.