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 skills add Agents365-ai/pi-plugin-cc --skill pi-result-handlinggit clone --depth 1 https://github.com/Agents365-ai/pi-plugin-ccWrote 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/agents365-ai/pi-plugin-cc/pi-result-handling)<a href="https://agentmods.dev/skills/agents365-ai/pi-plugin-cc/pi-result-handling"><img src="https://agentmods.dev/badge/skills/agents365-ai/pi-plugin-cc/pi-result-handling/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/agents365-ai/pi-plugin-cc/pi-result-handling"><img src="https://agentmods.dev/badge/skills/agents365-ai/pi-plugin-cc/pi-result-handling.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.00363 |
| Opus 5 | $0.00008 | $0.00181 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
pi-result-handling 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 10d 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.
This is a copy
86% identical to codex-result-handling — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Pi Result Handling
When the helper returns Pi output:
- Preserve the helper's verdict, summary, findings, and next steps structure.
- For review output, present findings first and keep them ordered by severity.
- Use the file paths and line numbers exactly as the helper reports them.
- Preserve evidence boundaries. If Pi marked something as an inference, uncertainty, or follow-up question, keep that distinction.
- Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
- If there are no findings, say that explicitly and keep the residual-risk note brief.
- If Pi made edits, say so explicitly and list the touched files when the helper provides them.
- For
pi:pi-companion-forwarder, do not turn a failed or incomplete Pi run into a Claude-side implementation attempt. Report the failure and stop. - For
pi:pi-companion-forwarder, if Pi was never successfully invoked, do not generate a substitute answer at all. - CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.
- If the helper reports malformed output or a failed Pi run, include the most actionable stderr lines and stop there instead of guessing.
- If the helper reports that setup is required (pi binary missing, no provider configured), direct the user to
/pi:setupand do not improvise alternate flows.
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.
- 10d ago First seen · 22 lines · 16 tokens per session scan A 005880a1bb44
pi-result-handling is a skill published in the GitHub repository Agents365-ai/pi-plugin-cc (44 stars, last pushed 26d ago), licensed Apache-2.0. It adds 16 tokens to every session and 363 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to codex-result-handling, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
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.
visual-acceptance
A visual final-review method for user-interface changes. It checks the rendered result with repeatable screenshots, pixel values, computed styles, and CSS layering checks across themes.
subagent-driven-development
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.
openspec
A specification-driven development process that records proposed software changes, implementation tasks, and updates to the project’s current behavior specifications.
ultra-task
Adaptive task supervision through subagents. Use when the user invokes "ultra-task", asks the main agent to act as a task supervisor, or wants subagents to perform most of a non-trivial task while the main agent coordinates and verifies. Do not use for simple one-step work, scripted Workflow pipelines, or…