reins

Install

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.

Security

Grade A, and why

reins 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 yesterday.

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.

plugin/.claude-plugin/plugin.json · 23 lines

What it actually says

{
  "name": "reins",
  "description": "Runtime security for AI agents. Blocks destructive actions before execution, routes high-risk operations through human approval, and maintains an immutable audit trail. Covers OWASP MCP Top 10, ASI Top 10, and Agentic Skills Top 10.",
  "version": "0.0.23",
  "author": {
    "name": "Pegasi"
  },
  "homepage": "https://app.pegasi.ai",
  "repository": "https://github.com/pegasi-ai/reins",
  "license": "Apache-2.0",
  "skills": "./skills",
  "hooks": "./hooks/hooks.json",
  "keywords": [
    "security",
    "ai-agents",
    "human-in-the-loop",
    "audit",
    "governance",
    "owasp",
    "policy-enforcement"
  ]
}

Files

What ships with it

1 file beside plugin.json 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.

Changes

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.

Related

Other plugins, from other repositories