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 skills/jakeefr/prism/prism-analyzenpx skills add jakeefr/prism --skill prism-analyzegit clone --depth 1 https://github.com/jakeefr/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/skills/jakeefr/prism/prism-analyze)<a href="https://agentmods.dev/skills/jakeefr/prism/prism-analyze"><img src="https://agentmods.dev/badge/skills/jakeefr/prism/prism-analyze.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.1 | $0.00033 | $0.00652 |
| Opus 5 | $0.00016 | $0.00326 |
| Sonnet 5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
prism-analyze 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 5d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prism-analyze
Analyze Claude Code session health using PRISM.
When to use
When the user asks to analyze their Claude Code sessions, check token usage, audit their CLAUDE.md, understand why sessions are failing, list their projects, or see what PRISM can see.
Before running
First check if PRISM is installed:
prism --version
If the command is not found, install it first:
pip install prism-cc
Then verify it installed correctly:
prism --version
Once confirmed installed, proceed with the analysis.
Usage
Run the analysis (reads JSONL from ~/.claude/projects/ by default):
prism analyze
If prism is not installed:
pip install prism-cc
prism analyze
For a specific project:
prism analyze --project <path>
For JSON output (useful for scripting):
prism analyze --json
For CLAUDE.md recommendations:
prism advise
List all projects PRISM can see:
prism projects
This prints each project name, session count, and last-active timestamp. Use it when the user asks what projects PRISM has data for, or to confirm that sessions are being recorded.
Agentsview data source
If the user has agentsview installed, PRISM can read from its SQLite database instead of raw JSONL. This gives real API token counts and agentsview's own health scores alongside PRISM's.
prism analyze --source agentsview
prism analyze --source agentsview --agentsview-db /path/to/sessions.db
prism analyze --source agentsview --json
DB path resolution when --agentsview-db is not specified:
AGENTSVIEW_DATA_DIR env → AGENT_VIEWER_DATA_DIR env → ~/.agentsview/sessions.db
Use --source agentsview when the user mentions agentsview, asks for real
token counts, or wants richer session data. Use the default (no flag) when
they just want a quick analysis from raw session files.
What PRISM shows
- Health scores (A-F) across 5 dimensions per project
- Token efficiency: CLAUDE.md re-read costs, compaction frequency
- Tool health: retry loops, edit-revert cycles, consecutive failures
- Context hygiene: compaction loss events, mid-task boundaries
- CLAUDE.md adherence: whether your rules are actually being followed
- Session continuity: resume success rate, truncated sessions
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.
- 5d ago First seen · 101 lines · 33 tokens per session scan A bb0b9633736b
prism-analyze is a skill published in the GitHub repository jakeefr/prism (22 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 652 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…