/prismor

name: prismor
description: Runtime security for AI coding agents. Use when about to install a package, paste a secret, run a destructive command, reach an unfamiliar host, govern MCP servers, pick a governance mode, set up a new workspace, respond to a changed-instruction-file notice, or recover from a Prismor block.

prismor: Runtime Security Skill

You are a coding agent. This skill keeps your tool calls safe: it blocks destructive shell commands, scores package installs against a live IOC feed, substitutes real secrets at execution time so they never enter model context, screens what tools return before it becomes your context, and audits every tool call to a local signed store.

This file is the decision tree. The pattern is: **trigger → which command → how to recover if blocked**. Detail lives in [`docs/`](./docs/); link out, don't duplicate.

---

When to invoke this skill

Trigger this skill (read the matching section below) the first time any of these happen in a session:

| Trigger | Section | |---|---| | New workspace, or unsure whether prismor is set up here | [Check state](#1-check-state-first-command-of-every-session) | | `prismor status` shows an outdated version, or user asks to upgrade | [Setup → keep current](#2-setup-run-once-per-workspace) | | User asks "how locked down is this repo?" / wants a whole posture, not one rule | [Governance modes](#3-governance-modes) | | About to run `npm/pip/cargo/uv/pnpm/yarn/go install …` | [Safe-command map → package install](#4-safe-command-map) | | About to put a real secret value into a tool call | [Safe-command map → secrets](#4-safe-command-map) | | About to run a shell command and you're uncertain it's safe | [Safe-command map → pre-check](#4-safe-command-map) | | Command or URL contains `169.254.169.254` or equivalent | [Safe-command map → cloud metadata](#4-safe-command-map) | | About to reach a host the project hasn't talked to before | [Safe-command map → egress](#4-safe-command-map) | | Tool output, prompt, or planned shell command contains SSNs, credit card numbers, or phone numbers | [Safe-command map → PII](#4-safe-command-map) | | Prompt or tool result asks you to change model parameters or override tool definitions | [Safe-command map → model manipulation](#4-safe-command-map) | | Prismor just blocked an action | [When blocked](#5-when-blocked) | | User asks "is this safe?" / "audit this" / "scan for leaks" | [On-demand audits](#6-on-demand-audits) | | User wants MCP servers governed, or asks why an MCP tool was blocked | [Enforcement surfaces → MCP gateway](#7-enforcement-surfaces) | | The agent in question can't be hooked (n8n, a hosted bot, a closed CLI) | [Enforcement surfaces → LLM proxy](#7-enforcement-surfaces) | | A built-in tool (`Bash`, `Read`, `Edit`) is missing or renamed | [Enforcement surfaces → mirror](#7-enforcement-surfaces) | | A **SECURITY NOTICE** says an instruction file changed, or a skill changed | [Instruction-file and skill integrity](#8-instruction-file-and-skill-integrity) | | User asks which agents/keys on this machine are unprotected ("shadow AI") | [On-demand audits](#6-on-demand-audits) | | User asks where their tokens/context are going | [On-demand audits](#6-on-demand-audits) |

Outside these triggers, do nothing. Prismor runs as a hook and intercepts in the background. You don't need to wrap every tool call.

---

1. Check state (first command of every session)

Run **one** command. It replaces the old `info` + `cloak status` + `status` trio:

prismor status

Read the output line by line:

• **`Hooks: not installed`** → go to [Setup](#2-setup-run-once-per-workspace). Without hooks, Prismor sees nothing.
• **`Hooks: claude (observe)`** → monitoring is on but only logging. Fine for the first session in a new repo. Recommend the user switch to `enforce` when they're ready (see [Setup](#2-setup-run-once-per-workspace)).
• **`Hooks: claude (enforce)`** → fully active. Proceed.
• **`Note:` lines** → status reports its own misconfigurations: the same agent hooked at *both* project and global scope (every call screened twice), or the two scopes disagreeing on mode. These are the user's to fix, and the printed command is the fix. Relay it, don't run it.
• **`Workspace:`** → check this is the repo you're actually working in. A hook installed against a different workspace evaluates your calls under *that* repo's policy, which is a real misconfiguration worth raising.
• **`Paused: yes`** → enforcement is suspended (logging continues). Say so before relying on a clean run; a command that passes while paused may block when it resumes.
• **`Cloaking: not installed`** → secret-prevention layer is off. Only required if the user works with API keys / tokens through the agent. If they do, run `prismor cloak install` then register secrets per [Safe-command map](#4-safe-command-map).
• **`LATEST SESSION` shows findings** → surface them to the user before starting new work.

Two follow-ups when the answer matters:

prismor mode show        # which governance posture this workspace runs, and any drift
prismor surfaces         # which enforcement surfaces are live, per agent on this host

If `prismor` is not on PATH, the workspace has never been set up. Go to [Setup](#2-setup-run-once-per-workspace).

---

2. Setup (run once per workspace)

**Setup is the user's command, not yours.** `prismor setup` and `prismor install-hooks` write agent hook configs and Prismor's own policy, so the self-protection rules block an agent that runs them — including `prismor install-hooks --help`. Print the commands below and let the human run them.

Preferred path (works for every supported agent):

pip install prismor
prismor setup            # interactive setup TUI

The wizard is four steps in observe mode. Choosing **enforce** inserts a [governance mode](#3-governance-modes) step — three named postures, each shown with its coverage and friction — and only if the user pick