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/agents365-ai/pi-plugin-cc/resultgit 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/commands/agents365-ai/pi-plugin-cc/result)<a href="https://agentmods.dev/commands/agents365-ai/pi-plugin-cc/result"><img src="https://agentmods.dev/badge/commands/agents365-ai/pi-plugin-cc/result.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.00013 | $0.00211 |
| Opus 5 | $0.00006 | $0.00105 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
result 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 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.
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
!node "${CLAUDE_PLUGIN_ROOT}/scripts/pi-companion.mjs" result "$ARGUMENTS"
Present the full command output to the user. Do not summarize or condense it. Preserve all details including:
- Job ID and status
- The complete result payload, including verdict, summary, findings, details, artifacts, and next steps
- File paths and line numbers exactly as reported
- Any error messages or parse errors
- Follow-up commands such as
/pi:status <id>and/pi:review
With --out-file <path>, the command instead writes the full result to that file and prints only a short summary. In that case, present the short summary verbatim and tell the user the file path — do not try to reconstruct the full output.
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 · 18 lines · 13 tokens per session scan A dc75975e87eb
result is a command published in the GitHub repository Agents365-ai/pi-plugin-cc (44 stars, last pushed 20d ago), licensed Apache-2.0. It adds 13 tokens to every session and 211 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-30.
Other commands, from other repositories
search
Search X (Twitter) and the web in real time with Grok, then summarize with sources.
review
Run a read-only Grok code review of your uncommitted changes or a branch.
result
Show the final output of a completed Grok job.
kill
Stop a running cli-dispatch worker session.
cancel
Cancel a running background Grok job.
ag-run
Delegate a task to the Antigravity (agy / Gemini) worker.