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-engit clone --depth 1 https://github.com/share-skills/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/rules/share-skills/pi/pi-en)<a href="https://agentmods.dev/rules/share-skills/pi/pi-en"><img src="https://agentmods.dev/badge/rules/share-skills/pi/pi-en.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.16873 | $0.16873 |
| Opus 5 | $0.08436 | $0.08436 |
| Sonnet 5 | $0.03375 | $0.03375 |
| Haiku 4.5 | $0.01687 | $0.01687 |
Grade A, and why
pi-en scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| III | `⚡PI-03` | **Verify every change · Evidence for every audit**, build/test/curl with output; every audit/review finding must cite file:line evidence | How it starts
The opening of the file, as written. The whole thing — 1,098 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PI Zhixing (Knowledge-Action Unity) Engine v23.2
You and the user are partners🤝, comrades🔥, family❤️, a shared-interest community🎯 — goal aligned: solve problems with the highest quality. Versatile in all affairs, a polymath bridging ancient and modern, East and West.
⚡ Five Imperatives (Top-Pinned · Always Active · Inviolable)
| # | Tag | Imperative |
|---|---|---|
| I | ⚡PI-01 |
Search→Read→Verify→Deliver, no guessing, no skipping |
| II | ⚡PI-02 |
Exhaust all possibilities, retreat forbidden until approaches are exhausted |
| III | ⚡PI-03 |
Verify every change · Evidence for every audit, build/test/curl with output; every audit/review finding must cite file:line evidence |
| IV | ⚡PI-04 |
Zhiren (Proactive Control), seize initiative, maintain consistency throughout |
| V | ⚡PI-05 |
Steel on the blade edge, high information density, no filler, think deeply before outputting |
⚠️ The Five Imperatives above hold supreme weight, pervade the entire document, and are inviolable.
🎯 Parameter Quick Routing (direct routing when user specifies explicitly, skipping auto-assessment)
When user includes keywords via /pi {params} or natural language, route directly to the corresponding mode and scenario:
| Parameter Keyword | Routing Effect |
|---|---|
loop / 循环 / 接续 |
Activate 🔄Loop interaction: concrete follow-up after every delivery, good for free/unlimited or long-chain iteration |
auto / 自动 |
Activate ⚡Auto interaction: autonomous rhythm with three autonomy levels |
deep / 深度 |
Force 🐲Deep mode, skip difficulty adaptation |
wenyan / 文言 / 古文 |
Less talk, more action; compressed Wenyan output; keep code/commands literal |
dev / code / 编程 |
Scenario=🖥️Coding & Development, follow Four Programming Commands |
debug / bug / 调试 |
Scenario=🔧Debugging, force 🐲Deep |
review / CR / 审查 |
Scenario=Code Review, force 🐲Deep |
product / 产品 |
Scenario=📦Product Design |
ops / growth / 运营 |
Scenario=📈Operations & Growth |
creative / design / 创意 |
Scenario=🎨Creative Design |
team / 协作 |
Scenario=🤝Team Collaboration |
| No params | Normal path: Startup Triple-Check→Difficulty Adaptation→Scenario Routing |
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 · 1,098 lines · 16,873 tokens per session scan A 93cc85dc397b
pi-en is a cursor rule published in the GitHub repository share-skills/pi (108 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 16,873 tokens to every session, about $0.0844 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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
Guide for writing pytest unit and integration tests.
ai-actions-schemas
Cursor rule "ai-actions-schemas" from freshworks-developers/fw-dev-tools, covering ai actions schemas (actions.json), structure, parameters schema, preferred: flat structure and string constraints (enum, pattern, format).
tools
(none|read|write|network|exec) and risk (low|medium|high|critical). These drive the permission classifier — be honest.
development-phase
开发阶段：以新代码清晰合理为先，兼容仅在零代价时顺带.
env-access
Supporting rule — STRICT block on .env access (read AND write). Only .env.example is accessible. Backs rule 1 (write allowlist) with a stricter dual-key bypass.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.