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.
git clone --depth 1 https://github.com/tznthou/claude-prismWrote 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/tznthou/claude-prism/pi-askall)<a href="https://agentmods.dev/commands/tznthou/claude-prism/pi-askall"><img src="https://agentmods.dev/badge/commands/tznthou/claude-prism/pi-askall/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/commands/tznthou/claude-prism/pi-askall"><img src="https://agentmods.dev/badge/commands/tznthou/claude-prism/pi-askall.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.02179 |
| Opus 5 | $0.00008 | $0.01090 |
| Sonnet 5 | $0.00003 | $0.00436 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
pi-askall 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask All Providers
Send the same question to Codex and Gemini in parallel, then Claude synthesizes. Multiple AI viewpoints on any topic — not limited to code.
Execution
Dispatch rules (v0.13.0+): For parallel provider consultation, use the
Agenttool withsubagent_type: "general-purpose"to spawn two parallel sub-agents — NOT twoBashtool calls in a single main-conversation response. Main-conversation Bash is a structural FIFO queue: the second Bash waits for the first to finish (delta ≈ first_execprecisely, measured N=7 across two capacity slots), which defeats the parallel intent. Sub-agent fan-out dispatches Bash calls truly in parallel (median delta 2.8s, N=13), saving roughly 28% wall-clock on a two-provider call.Inside each sub-agent, run
call-codex.sh/call-gemini.shin foreground synchronous mode withtimeout: 600000(Bash tool's 10-minute ceiling). Do not use&,nohup, orrun_in_background: true— Claude Code 2026-04+ has an auto-background child-lifecycle regression that silently kills the child (output file stays 0 bytes). If a sub-agent's Bash returns empty stdout, the Bash template below falls back to reading the caller-owned$OUT_PATHfile (v0.14.3+, wrappertees here viaCLAUDE_PRISM_OUT_TMP).
1. Build the prompt
Use $ARGUMENTS as the base question.
If $ARGUMENTS references a file path (e.g., src/config.ts or ./README.md):
- Read the file with the Read tool
- Append the file content as context to the question sent to both providers
If $ARGUMENTS references recent conversation context (e.g., "the plan we just discussed", "this approach"):
- Claude summarizes the relevant context into a self-contained question
- The question sent to providers must be understandable without conversation history
If $ARGUMENTS is empty, ask the user: "What topic or question should I get multiple perspectives on?"
2. Frame the prompt, then fan out via sub-agents
Step 2a — Build the framed wrapper (compose once, used by both providers):
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 · 154 lines · 16 tokens per session scan A cad7f66497c0
pi-askall is a command published in the GitHub repository tznthou/claude-prism (10 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 2,179 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
conventions-check
Check AGENTS.md, CLAUDE.md, and the projected agent artifacts (skills, subagents, commands) against the repo's conventions.
register-plugin-asset
A project command for adding a distributable command, agent, or agent skill to a plugin manifest, the file that lists what a plugin provides.
challenge
Adversarial review — run pre-mortem, war-game, and logic-torturing analysis on current changes.
logic-diff
Check two code versions for semantic equivalence — use after a refactor or rewrite.
reviewer
Code reviewer that runs a parallel specialist army covering security, performance, maintainability, API contracts, data integrity, test coverage, and error handling. Trigger on code review, review, PR review, pull request, or review army.
README
Repo-development slash commands (NOT part of the distributed plugin surface).