ginkgo

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

ginkgo 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

{
  "name": "ginkgo",
  "owner": {
    "name": "Onsi Fakhouri",
    "url": "https://github.com/onsi"
  },
  "metadata": {
    "description": "Skills for writing, running, and debugging Go tests with Ginkgo — the expressive BDD testing framework, paired with Gomega.",
    "homepage": "https://onsi.github.io/ginkgo/"
  },
  "plugins": [
    {
      "name": "ginkgo",
      "source": "./plugins/ginkgo",
      "description": "Write, run, and debug Ginkgo/Gomega test suites in Go: the tree-construction mental model, the full node and decorator surface, tables and generated specs, parallelism, filtering, timeouts and async, CI configuration, and JSON-first failure diagnosis."
    }
  ]
}

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