gauntlet-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

gauntlet-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 · 19 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
  "name": "gauntlet-marketplace",
  "version": "1.0.0",
  "description": "Marketplace for the gauntlet plugin.",
  "owner": {
    "name": "Rebel028",
    "url": "https://github.com/Rebel028"
  },
  "plugins": [
    {
      "name": "gauntlet",
      "description": "Run an idea or design through a gauntlet of independent skeptic subagents — formalist, practitioner, consumer-advocate, historian, threat-modeler — each attacking from a different angle so the flaw surfaces before you commit. For vetting one design, choosing between options, or pressure-testing anything irreversible.",
      "source": "./dist/claude",
      "category": "development"
    }
  ]
}

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