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/ronkupper/prism/prism-statusgit clone --depth 1 https://github.com/Ronkupper/PRISMWhat 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.00033 | $0.00446 |
| Opus 5 | $0.00016 | $0.00223 |
| Sonnet 5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
prism-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.
What it actually says
Render the PRISM engagement's current state — the Desk's STATE view, built from verified repo state, never from memory.
Optional view selector (map, timeline, or empty for both):
$ARGUMENTS
Then proceed:
- Load the framework if it is not already active: read
PRISM_core.md, then fetchreference/lanes-ui.md(the PRISM UI and trajectory-view reference). - Re-sync canonical state (the HEALTH view). Work from a fresh
pull --rebaseof the live tail; confirm HEAD matches the mirror and the What's next pointer is present. If the repo is unreachable, degrade to the attached Master and say so. - Render the STATE view — two modes, side by side, each in its own form (not
fused):
- a dependency / critical-path map — what gates what, what runs in parallel, where the bottleneck is, with the critical-path callout; and
- a progress timeline — where am I, what's done (● complete · ◉ you are
here · ○ pending).
Use the stable visual language, the colored status encoding, and a code → real-name
legend translating pass codes (
A11,R1, …) to their objectives — rendered from the live Master's Prompt Strategy and Dispatch register, not re-transcribed.
- Close with the one next action (the ACTION line) so the view hands off
cleanly to
/prism-whats-next.
This command is a Claude-Skill convenience for summoning the state view on demand; it changes no framework mechanic. Asking "show the trajectory / where are we" in plain language is equivalent, and is the portable form on every other vendor.
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 · 36 lines · 33 tokens per session scan A 32671aabc281
prism-status is a command published in the GitHub repository Ronkupper/PRISM (5 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 446 once invoked, about $0.0002 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
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
propose
Manage parked phase proposals in the audit manifest — list them, materialize one (or all) into live phases, or drop one. Proposals are parked by /audit:init when the user declines (some of) the synthesized plan; materialization is a move, not a re-synthesis.