Prepare Prism instruments for delivery to subagents, agents, or skills. Resolves instrument names to absolute paths and returns an instruction block (path table + read directives + brief summary) ready to paste into a subagent prompt. Intended as the second step after `/prism search`. Triggers on "/prism fetch stride owasp-top10", "load instruments", "fetch instruments for my subagent", "instrument load", "attach lenses to subagent"
Prepare selected Prism instruments as an instruction block that a subagent can consume directly.
If /prism search is "discover what exists," fetch is "get the
selected ones ready."
/prism search to find candidates → fetch to
equip selected instruments.Accepts one or more of the following:
stride, owasp-top10,
systems-thinking, etc. Must match a name value in catalog.yml.catalog.yml and ask
one clarifying question. Do not guess.Prism stores instruments in three layers. Merge with precedence project > global > bundle:
Bundle layer (read-only) — instruments shipped with the plugin.
<plugin-root>/catalog.yml<plugin-root>/library/Global layer (optional) — user-wide instruments.
~/.claude/prism/catalog.yml~/.claude/prism/library/Project layer (optional) — project-scoped instruments.
./.claude/prism/catalog.yml (relative to CWD)./.claude/prism/library/catalog.yml from all three layers and extract the path field
for each requested instrument.name collision, higher-precedence layer wins. Note overrides in
output.path to an absolute path relative to its layer root.one_liner and class from frontmatter as the brief summary.Return a copy-pasteable text block for subagent prompts:
## Prism Instruments — Subagent Directive
Read the following instrument files with the Read tool and follow
each file's core procedure section in your analysis workflow.
| # | name | class | summary | path |
|---|------|-------|---------|------|
| 1 | stride | lens | Identify threats per STRIDE category | /full/path/to/stride.md |
| 2 | owasp-top10 | lens | Run OWASP Top 10 checklist | /full/path/to/owasp-top10.md |
### Core section guide by class
- **lens**: Follow the "Analytical Procedure" steps in order
- **frame**: Apply "Categories" + "Classification Procedure"
- **model**: Apply "Core Variables" + "Application Procedure"
- **stance**: Set analysis perspective via "Guiding Questions"
- **heuristic**: Use "The Rule" + "When It Applies" as checkpoints
If overrides occurred, append a note below the table: