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/statusgit 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/status)<a href="https://agentmods.dev/commands/agents365-ai/pi-plugin-cc/status"><img src="https://agentmods.dev/badge/commands/agents365-ai/pi-plugin-cc/status.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.00015 | $0.00187 |
| Opus 5 | $0.00008 | $0.00093 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
status 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 3d 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
88% identical to status — 4 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
!node "${CLAUDE_PLUGIN_ROOT}/scripts/pi-companion.mjs" status "$ARGUMENTS"
If the user did not pass a job ID:
- Render the command output as a single Markdown table for the current and past runs in this session.
- Keep it compact. Do not include progress blocks or extra prose outside the table.
- Preserve the actionable fields from the command output, including job ID, kind, status, phase, elapsed or duration, summary, and follow-up commands.
If the user did pass a job ID:
- Present the full command output to the user.
- Do not summarize or condense it.
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.
- 3d ago First seen · 18 lines · 15 tokens per session scan A f1608a2cc7c3
status is a command published in the GitHub repository Agents365-ai/pi-plugin-cc (43 stars, last pushed 19d ago), licensed Apache-2.0. It adds 15 tokens to every session and 187 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to status, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.
result
Show the final output of a completed Grok job.
foreground
Run the connector in the current terminal.
resume-from
Continue a session from another coding agent or another Claude Code profile.
create-drizzle-repository
Scaffold a new Drizzle-backed repository by defining a domain port, implementing it with typed Drizzle queries, and wiring it into DI to provide consistent, testable persistence whenever a use case needs read/write access to a new or refactored table.