cigar

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

cigar 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 2d 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.

adapters/claude-code/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "cigar",
  "displayName": "CIGAR",
  "version": "0.9.4",
  "description": "Deterministic, inspectable, governed context for Claude Code through public hooks and MCP.",
  "author": {
    "name": "CIGAR contributors"
  },
  "homepage": "https://github.com/CIGAR/cigar",
  "repository": "https://github.com/CIGAR/cigar",
  "license": "Apache-2.0",
  "keywords": [
    "context",
    "governance",
    "mcp",
    "replay"
  ]
}

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