github-keeper

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

github-keeper 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.

plugins/github-keeper/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "github-keeper",
  "version": "0.4.0",
  "description": "Make a public GitHub repo well-made and honest. /readme audits and elevates a README — deriving the hero, voice, badges, and sections from the PROJECT's own identity (fidelity gate, propose-and-confirm), with free-form targeted edits; /opensource adds the community-health files, an honest CI gate, and the right repo settings. Honesty-first; confirms outward actions.",
  "author": {
    "name": "Giusto Piedimonte"
  },
  "keywords": [
    "readme",
    "documentation",
    "open-source",
    "github",
    "community-health",
    "ci",
    "badges",
    "public-repo",
    "maintenance"
  ]
}

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