coding-agent-plugins

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

coding-agent-plugins 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.

.claude-plugin/marketplace.json · 34 lines

What it actually says

{
  "name": "coding-agent-plugins",
  "version": "1.0.0",
  "description": "Collection of plugins for Claude Code and OpenCode",
  "owner": {
    "name": "Saatvik Arya",
    "email": "[email protected]"
  },
  "plugins": [
    {
      "name": "ni",
      "description": "Universal package manager - automatically translates npm/yarn/pnpm/bun commands to use ni",
      "version": "1.0.1",
      "author": {
        "name": "Saatvik Arya",
        "email": "[email protected]"
      },
      "source": "./plugins/ni",
      "category": "development"
    },
    {
      "name": "wt",
      "description": "Nudges git worktree add toward the wt CLI (syncs gitignored files + installs deps)",
      "version": "1.0.0",
      "author": {
        "name": "Saatvik Arya",
        "email": "[email protected]"
      },
      "source": "./plugins/wt",
      "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