system

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

system 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 yesterday.

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/system/.claude-plugin/plugin.json · 23 lines

What it actually says

{
  "name": "system",
  "version": "1.2.0",
  "description": "System health, maintenance, and project setup",
  "author": {
    "name": "Claude Code Framework"
  },
  "keywords": ["system", "health", "audit", "maintenance", "setup"],
  "commands": [
    "./commands/audit.md",
    "./commands/cleanup.md",
    "./commands/system:status.md"
  ],
  "agents": [
    "./agents/auditor.md",
    "./agents/reasoning-specialist.md"
  ],
  "skills": [
    "./skills/project-setup"
  ],
  "license": "MIT"
}

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