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 instructions/code-yeongyu/pi-rules/reviewgit clone --depth 1 https://github.com/code-yeongyu/pi-rulesWhat 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.00024 |
| Opus 5 | $0.00012 | $0.00012 |
| Sonnet 5 | $0.00005 | $0.00005 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
pi-rules review.instructions.md 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 yesterday.
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
Review
Reviewers MUST check tests pass before approving.
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.
- yesterday First seen · 9 lines · 24 tokens per session scan A 587d5dc67334
pi-rules review.instructions.md is an instructions file published in the GitHub repository code-yeongyu/pi-rules (10 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session, 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-31.
Other instructions, from other repositories
AGENTS.md AGENTS.md
Instructions for Anbeeld/AGENTS.md, covering global instructions, priorities, boundaries, uncertainty and evidence.
ruleblast AGENTS.md
Instructions for Kpoiut/ruleblast, covering ruleblast repository instructions, evidence before confidence, change discipline and before a commit.
codex-rules AGENTS.md
Instructions for code-yeongyu/codex-rules, covering repository conventions, style, commands, constraints and don'ts.
balakit AGENTS.md
AGENTS.md instructions for afaraha8403/balakit, covering project rules, base rules, the meta-principle, ai behavior & communication (dual-mode) and think before coding.
deep-init copilot-instructions.md
Instructions for deepfusionlabs/deep-init, covering repository instructions (copilot projection), kemal — agent context, architecture, components (7) and critical to know (non-obvious, load-bearing).
agentic-coding-workflow AGENTS.md
Instructions for abhilash-m96/agentic-coding-workflow, covering agentic coding workflow, rules, step 1 — understand the full scope, step 2 — propose the chunk plan and step 3 — write the finalised plan.