pagerduty-claude-code-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

pagerduty-claude-code-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 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 · 18 lines

What it actually says

{
    "name": "pagerduty-claude-code-plugins",
    "description": "A collection of Claude Code plugins developed by PagerDuty to enhance code quality and security through risk scoring and incident correlation.",
    "owner": {
        "name": "PagerDuty"
    },
    "plugins": [
        {
            "name": "pagerduty",
            "source": "./",
            "description": "Pre-commit risk assessment using PagerDuty incident history, and PagerDuty skill creation for AI agents (Early Access).",
            "version": "1.1.0",
            "author": {
                "name": "PagerDuty"
            }
        }
    ]
}

Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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