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.
npx skills add PagerDuty/cursor-plugin --skill pagerduty-mcp-setupgit clone --depth 1 https://github.com/PagerDuty/cursor-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pagerduty/cursor-plugin/pagerduty-mcp-setup)<a href="https://agentmods.dev/skills/pagerduty/cursor-plugin/pagerduty-mcp-setup"><img src="https://agentmods.dev/badge/skills/pagerduty/cursor-plugin/pagerduty-mcp-setup.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.00769 |
| Opus 5 | $0.00029 | $0.00385 |
| Sonnet 5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
pagerduty-mcp-setup 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 7d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: Before using the PagerDuty MCP or doing any other investigation related to PagerDuty, you must follow these directions and make sure that the following requirements are met.
Context
The configuration for the MCP of the PagerDuty Plugin lives in the following directory relative to the path to this SKILL.md file: ../../mcp.json
In a non-configured state, the Authorization header contains the placeholder Token ${PAGERDUTY_API_TOKEN}.
IMPORTANT: Before using the PagerDuty MCP you MUST ensure that this placeholder has been replaced with a real PagerDuty User API token.
The PagerDuty-hosted MCP service expects the header to look like this:
{
"Authorization": "Token your-pagerduty-api-token-here"
}
If this has not been customized for the user, you should not do anything except tell the user that the PagerDuty MCP is not configured yet and help them finish setup.
Do not continue investigating PagerDuty or checking PagerDuty MCP tool schemas until the token is configured.
Steps
Before continuing, take the following steps:
- Read the
mcp.jsonfile in the plugin directory. This is in the grandparent directory relative to this SKILL.md file (../../mcp.json). - If the file still contains
Token ${PAGERDUTY_API_TOKEN}or${PAGERDUTY_API_TOKEN}, stop immediately. Tell the user the PagerDuty MCP is not configured yet. - In that message, do all of the following:
- Cite
mcp.jsonand specifically point to theheaders.Authorizationlines in that file so the user knows exactly what to edit. - Include a JSON code block with the current
mcp.jsonconfig so they can copy it directly. - Tell them to replace
${PAGERDUTY_API_TOKEN}with their PagerDuty User API token, keeping theTokenprefix in the Authorization header. - Tell them they can follow PagerDuty's API token instructions here:
https://support.pagerduty.com/main/docs/pagerduty-mcp-server-integration-guide#generate-your-pagerduty-api-token - Do not ask them to send you the token.
- Do not inspect PagerDuty MCP tools or continue the PagerDuty task yet.
- Cite
- Once the token has been added to
mcp.json, tell the user to refresh Cursor by opening the Command Palette (⌘⇧Pon Mac orCtrl+Shift+Pon Windows/Linux) and runningReload Window. Use the current operating system to decide what keybinding to show. - Continue on to using the PagerDuty MCP.
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.
- 7d ago First seen · 59 lines · 58 tokens per session scan A 85c936c2ab9f
pagerduty-mcp-setup is a skill published in the GitHub repository PagerDuty/cursor-plugin (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 58 tokens to every session and 769 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…