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/pasky/pi-side-agents/agent-setupnpx skills add pasky/pi-side-agents --skill agent-setupgit clone --depth 1 https://github.com/pasky/pi-side-agentsWrote 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/pasky/pi-side-agents/agent-setup)<a href="https://agentmods.dev/skills/pasky/pi-side-agents/agent-setup"><img src="https://agentmods.dev/badge/skills/pasky/pi-side-agents/agent-setup.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 | $0.00024 | $0.02780 |
| Opus 5 | $0.00012 | $0.01390 |
| Sonnet 5 | $0.00005 | $0.00556 |
| Haiku 4.5 | $0.00002 | $0.00278 |
Grade A, and why
agent-setup 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 4d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Agent Setup
Set up the pi-side-agents lifecycle scripts for this project.
Initial first time setup (no .pi/side-agent* yet): Work through two phases: interview, then file creation. Finish by backing up this agent-setup SKILL.md to .pi/side-agents/agent-start~/ for easy future upgrades.
Update setup: Chat with the user about what needs changing, use file examples below as reference for comparison.
Upgrade setup to new pi-side-agents version: Diff this file with the current backup .pi/side-agents/agent-start~/
and discuss the changes to apply (or not) with the user. When upgrade is finished, update the backup to the current version.
Important (local-only files): everything this skill creates is under .pi/ and is runtime/local configuration. Do not git add, git add -f, or commit these files. They should remain untracked. If they were accidentally committed, remove them from git tracking while keeping them locally.
Phase 1: Interview
Ask the user the following questions. You may ask them all at once or one at a time — use your judgment based on how they engage.
-
Main branch name – What is the primary integration branch? (default:
main) -
Bootstrap steps – Does each agent worktree need custom setup before work begins? For example:
npm install, copying.envfiles, running migrations. If yes, what commands specifically? -
Finish policy – When an agent finishes, should it:
- Rebase locally, then fast-forward into the main branch in the parent checkout (default), or
- Open a pull request instead?
-
Overwrite existing files – If
.pi/side-agent-start.shor similar already exist, overwrite them? (default: no — skip existing files)
Before asking the questions, autonomously try to answer questions 1, 2 and 4, and propose project-specific answers to the user.
Collect all answers before proceeding to Phase 2.
Phase 2: Create Setup Files
Determine the git repo root:
GIT_ROOT=$(git rev-parse --show-toplevel)
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.
- 4d ago First seen · 314 lines · 24 tokens per session scan A 8171340b674c
agent-setup is a skill published in the GitHub repository pasky/pi-side-agents (191 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 2,780 once invoked, about $0.0001 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…