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/cohemm/prism/analyzenpx skills add cohemm/prism --skill analyzegit clone --depth 1 https://github.com/cohemm/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/cohemm/prism/analyze)<a href="https://agentmods.dev/skills/cohemm/prism/analyze"><img src="https://agentmods.dev/badge/skills/cohemm/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 | $0.00054 | $0.01836 |
| Opus 5 | $0.00027 | $0.00918 |
| Sonnet 5 | $0.00011 | $0.00367 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Perspective Analysis
General-purpose analysis engine. Any topic is seeded, researched, and analyzed from dynamically generated perspectives with Socratic verification.
All analysis processing is orchestrated by the MCP server internally. This skill is a thin wrapper that:
- Collects user input (topic description)
- Calls
prism_analyzeto start the analysis pipeline (ontology scope is auto-resolved from brownfield defaults by the MCP server) - Polls
prism_task_statusfor progress updates - Retrieves results via
prism_analyze_resultwhen complete - Presents the final report to the user
Ontology Scope Resolution (Automatic)
The MCP server automatically resolves ontology scope using this priority:
- Explicit
ontology_scopeparameter — if provided via config, used as-is - Brownfield default repositories — all repos with
is_default=1inprism.dbare merged into scope sources - Error — if neither is available, the server returns an error asking the user to set up brownfield defaults first
No user interaction is required for ontology scope mapping. Use prism:brownfield to configure default repositories before running analysis.
Config-Based Customization
Wrapper skills (e.g., /prd) can customize analyze behavior by providing a config file. The config path is passed via $ARGUMENTS as --config <path>.
When this skill runs from Codex, pass adaptor: "codex" in the prism_analyze call. When it runs from Claude Code, pass adaptor: "claude". Do not rely on process-global runtime defaults when the caller knows the host runtime.
Config Schema
{
"topic": "What to analyze (overrides description if provided)",
"input_context": "Path to input file (e.g., PRD file path)",
"report_template": "Path to custom report template (overrides default)",
"seed_hints": "Additional guidance for seed analyst (e.g., 'Focus on policy domain extraction')",
"session_id": "Pre-generated session ID (optional — task_id becomes analyze-{session_id})",
"model": "Claude model override (default: claude-sonnet-4-6)"
}
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- prompts/analyst-prompt-structure.md 3.8 KB
- prompts/finding-protocol.md 2.2 KB
- prompts/perspective-generator.md 6.1 KB
- prompts/seed-analyst.md 7.3 KB
- prompts/verification-protocol.md 3.3 KB
- protocols/ontology-scope-mapping.md 3.5 KB
- protocols/ontology-scope-schema.md 4.4 KB
- protocols/prerequisite-gate.md 1.7 KB
- protocols/team-teardown.md 553 B
- protocols/worker-preamble.md 1.0 KB
- scripts/merge-perspective-injection.sh 1.5 KB runs code
- templates/report.md 2.2 KB
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 · 225 lines · 54 tokens per session scan A 27e34ab64485
analyze is a skill published in the GitHub repository cohemm/prism (5 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,836 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…