discover

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

discover 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.

.claude-plugin/plugin.json · 27 lines

What it actually says

{
  "name": "discover",
  "version": "0.4.1",
  "description": "Discover product opportunities, validate hypotheses, and create evidence-backed PRDs in your repository",
  "author": {
    "name": "shinpr",
    "url": "https://github.com/shinpr"
  },
  "homepage": "https://github.com/shinpr/claude-code-discover",
  "repository": "https://github.com/shinpr/claude-code-discover.git",
  "license": "MIT",
  "keywords": [
    "product-discovery",
    "hypothesis-driven",
    "prd",
    "validation",
    "product-management"
  ],
  "agents": [
    "./agents/prd-reviewer.md",
    "./agents/codebase-analyzer.md",
    "./agents/hypothesis-verifier.md",
    "./agents/knowledge-distiller.md",
    "./agents/prototype-generator.md"
  ]
}

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