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 rules/share-skills/pi/pi-visualizegit clone --depth 1 https://github.com/share-skills/piWhat 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.00297 | $0.00297 |
| Opus 5 | $0.00148 | $0.00148 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
pi-visualize 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 2d 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.
What it actually says
PI Visualizer in Cursor
To visualize your PI decision history locally:
1) Generate a standalone (offline) HTML
/pi visualize
This builds the standalone frontend, embeds your local archive (default: ~/.pi/decisions), and opens the resulting file:// HTML unless --no-open is passed.
Headless / CI usage:
/pi visualize --no-open --output /tmp/pi.html
2) Live local preview (opt-in)
When you want the browser to auto-refresh as sanitized archive files change, use the CLI live mode (loopback HTTP server + polling):
cd visualize && npm run dev
Notes:
- Development server runs on Vite with hot module replacement.
- Production server uses
npm run serveron port 3141.
3) Source selection
Default source is ~/.pi/decisions. You can point to a specific directory:
/pi visualize --source path/to/.pi/decisions
Privacy / sync
- The visualizer runs locally.
--bind-github/--github-worktreecurrently perform local git worktree history sync (sanitized sessions + local commits). Remote push is manual / out of scope.
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.
- 2d ago First seen · 48 lines · 297 tokens per session scan A 7f7804abe493
pi-visualize is a cursor rule published in the GitHub repository share-skills/pi (108 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 297 tokens to every session, about $0.0015 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 cursor rules, from other repositories
testing
Testing rules for vitest suite.
tools
(none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.
typescript
TypeScript style rules, scoped to .ts files.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.