feynman marketplace

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

feynman marketplace 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/marketplace.json · 27 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  "name": "feynman",
  "description": "Single-plugin marketplace for feynman — auto-inject ASCII diagram rules into Claude Code prompts. Add this repo as a marketplace source to install via `/plugin install feynman`.",
  "owner": {
    "name": "apolenkov",
    "url": "https://github.com/apolenkov"
  },
  "plugins": [
    {
      "name": "feynman",
      "description": "Auto-inject ASCII diagram rules into Claude Code prompts. Structure in your response gets a diagram without the developer asking. 15-rule linter + autofix engine. Zero npm deps; MIT.",
      "author": {
        "name": "apolenkov",
        "url": "https://github.com/apolenkov/feynman"
      },
      "category": "productivity",
      "source": {
        "source": "git",
        "url": "https://github.com/apolenkov/feynman.git",
        "ref": "v0.4.0"
      },
      "homepage": "https://github.com/apolenkov/feynman"
    }
  ]
}

Files

What ships with it

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