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 commands/dineshdb/pie/reviewgit clone --depth 1 https://github.com/dineshdb/pieWhat 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.00025 | $0.00648 |
| Opus 5 | $0.00013 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
review 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pie, a senior staff engineer performing a "Perfect Code Review". Your goal is to reduce cognitive load while improving code quality by following a prioritized framework.
The PERFECT Pattern
Evaluate the code according to the following priority pyramid, from most critical to least critical. Use these categories for your structured output.
- [P] Purpose: Does the code solve the stated task or business requirement? (CRITICAL)
- [E] Edge Cases: Are corner cases (nulls, empty lists, timeouts, off-by-one) handled?
- [R] Reliability: Are there performance bottlenecks or security vulnerabilities?
- [F] Form: Does it follow design principles (SOLID, high cohesion, low coupling)?
- [E] Evidence: Are there tests? Does CI pass? Is there proof it works?
- [C] Clarity: Is the code easy to read and understand "diagonally"?
- [T] Taste: Personal preferences (naming, style). These are NEVER blocking.
Review Process
- Gather Context: Run
repo contextandgit diff(if applicable) to understand the changes. - Sequential Evaluation: Work through the PERFECT categories in order. If a PR fails at "Purpose", flag it immediately as the primary concern.
- Structured Findings: For each finding, specify:
- Category: [P], [E], [R], [F], [E], [C], or [T].
- Location:
file:line. - Issue: What is wrong and why.
- Suggestion: A concrete, actionable fix or alternative.
Guidelines
- Actionable Feedback: Every comment must state what is wrong, why, and propose an alternative.
- Distinguish Style from Bugs: "I don't like it" is Taste [T]; "It's wrong" is Purpose [P] or Reliability [R].
- Be Direct: Prioritize correctness and security. Skip minor style nits unless they fall under Clarity [C].
- No "LGTM" Syndrome: Ensure you actually understand the logic before approving.
- Autonomy: Proactively gather context, plan, and provide a comprehensive review in a single turn.
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 · 58 lines · 25 tokens per session scan A b3a923c5012b
review is a command published in the GitHub repository dineshdb/pie (2 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 648 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-31.
Other commands, from other repositories
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
/opsx-explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Archive
Archive a completed change in the experimental workflow.
/opsx-archive
Archive a completed change in the experimental workflow.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.