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 agentmods add skills/romiluz13/pi-agent-skills/pi-cli-workspacenpx skills add romiluz13/pi-agent-skills --skill pi-cli-workspacegit clone --depth 1 https://github.com/romiluz13/pi-agent-skillsWrote 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/pi-agent-skills/pi-cli-workspace)<a href="https://agentmods.dev/skills/romiluz13/pi-agent-skills/pi-cli-workspace"><img src="https://agentmods.dev/badge/skills/romiluz13/pi-agent-skills/pi-cli-workspace.svg" alt="Measured on agentmods" 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.00214 | $0.03406 |
| Opus 5 | $0.00107 | $0.01703 |
| Sonnet 5 | $0.00043 | $0.00681 |
| Haiku 4.5 | $0.00021 | $0.00341 |
Grade A, and why
pi-cli-workspace 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pi CLI and workspace
Answer only from pi-mono/ sources listed below. If something is not in the tree, say you cannot confirm from the corpus.
Grounding (read in order)
pi-mono/packages/coding-agent/README.md— product surface, commands, customization.pi-mono/packages/coding-agent/docs/skills.md— skill locations,/skill:name, frontmatter, collisions.pi-mono/packages/coding-agent/docs/settings.md— settings locations and keys.pi-mono/AGENTS.md— maintainer rules when editing pi-mono itself.pi-mono/packages/coding-agent/docs/compaction.md— auto-compaction triggers, cut-point algorithm,reserveTokens/keepRecentTokenssettings, chained compactions, branch summarization.pi-mono/packages/coding-agent/docs/session.md— JSONL session format,~/.pi/agent/sessions/paths, entry types (message, compaction, branch_summary, custom, label),buildSessionContext()assembly.pi-mono/packages/coding-agent/docs/tree.md—/treevs/fork, branch navigation, summarization options, tree UI keybindings.pi-mono/packages/coding-agent/docs/providers.md— subscription OAuth (/login), API-key providers,auth.json, env-var credential table, cloud providers (Azure, Bedrock, Vertex).pi-mono/packages/coding-agent/docs/models.md—models.jsonfor Ollama/vLLM/LM Studio,compatflags,modelOverrides, provider-level config.pi-mono/packages/coding-agent/docs/custom-provider.md— extension-registered providers viaregisterProvider(), OAuth flows, proxy patterns.pi-mono/packages/coding-agent/docs/terminal-setup.md— Kitty keyboard protocol, Ghostty/iTerm/terminal keybinding caveats.pi-mono/packages/coding-agent/docs/tmux.md— tmuxextended-keys/csi-uso modified keys work inside pi.pi-mono/packages/coding-agent/docs/windows.md— Windows bash discovery order (shellPathsetting, Git Bash, PATH).pi-mono/packages/coding-agent/docs/termux.md— running pi on Android via Termux (install, clipboard, storage).pi-mono/packages/coding-agent/docs/shell-aliases.md— non-interactive bash andshellCommandPrefixto expand aliases from dotfiles.pi-mono/packages/coding-agent/docs/development.md— local development setup,pi-test.sh, fork/rebrand viapiConfig, test commands.- Implementation (for precedence and prompt wiring):
pi-mono/packages/coding-agent/src/core/package-manager.ts—resourcePrecedenceRankcomment block (ordering intent).pi-mono/packages/coding-agent/src/core/resource-loader.ts—reload()skill path merge (cliEnabledSkills,enabledSkills,additionalSkillPaths).pi-mono/packages/coding-agent/src/core/skills.ts—loadSkills,formatSkillsForPrompt, name collision handling.pi-mono/packages/coding-agent/src/core/system-prompt.ts— default harness text andhasReadgate for skills XML.pi-mono/packages/coding-agent/src/core/agent-session.ts—_expandSkillCommandinlines/skill:namebody.
pi-mono/packages/coding-agent/README.md§Editor —@fuzzy-search, Tab completion, Ctrl+V image paste,!/!!bash commands.pi-mono/packages/coding-agent/README.md§Message Queue — steering (Enter) vs follow-up (Alt+Enter),steeringMode/followUpMode/transportsettings.pi-mono/packages/coding-agent/README.md§Modes, §CLI Reference — interactive,-p/--print,--mode json,--mode rpc, piped stdin.pi-mono/packages/coding-agent/README.md§CLI Reference — full flag table,@files,--tools,--no-tools,--no-extensions,--no-skills,--no-prompt-templates,--no-themes, resource control.pi-mono/packages/coding-agent/README.md§Environment Variables —PI_CODING_AGENT_DIR,PI_PACKAGE_DIR,PI_SKIP_VERSION_CHECK,PI_CACHE_RETENTION,VISUAL/EDITOR.pi-mono/packages/coding-agent/README.md§Philosophy — what core intentionally omits (no MCP, no sub-agents, no permission popups, no plan mode, no built-in todos, no background bash); everything buildable via extensions.
What ships with it
1 file 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 · 87 lines · 214 tokens per session scan A eb4b8ce63678
pi-cli-workspace is a skill published in the GitHub repository romiluz13/pi-agent-skills (18 stars, last pushed 4mo ago), licensed MIT. It adds 214 tokens to every session and 3,406 once invoked, about $0.0011 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…