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 iLert/ilert-cli --skill migrate-from-pagerdutygit clone --depth 1 https://github.com/iLert/ilert-cliWrote 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/ilert/ilert-cli/migrate-from-pagerduty)<a href="https://agentmods.dev/skills/ilert/ilert-cli/migrate-from-pagerduty"><img src="https://agentmods.dev/badge/skills/ilert/ilert-cli/migrate-from-pagerduty/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ilert/ilert-cli/migrate-from-pagerduty"><img src="https://agentmods.dev/badge/skills/ilert/ilert-cli/migrate-from-pagerduty.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.07913 |
| Opus 5.5 | $0.00006 | $0.03165 |
| Sonnet 5.5 | $0.00003 | $0.01583 |
| Haiku 4.5 | $0.00002 | $0.00791 |
Grade B, and why
migrate-from-pagerduty scanned grade B with 2 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
* **A config or header file the user writes once**, `chmod 600`, that you Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Token token=$PD_TOKEN" # the shell expands this first How it starts
The opening of the file, as written. The whole thing — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating from PagerDuty to ilert
The two products use overlapping words for different objects. Two of those collisions cause most migration defects, and neither is visible from the API spec.
For ilert's own semantics and the CLI behaviour behind a bulk import, read the
ilert-essentials skill alongside this one. Where PagerDuty's own data lives —
and how to hold a foreign API key while you read it — is under Reading the
PagerDuty side below; start there when the job is extraction rather than design.
The two traps
A PagerDuty Service is not an ilert Service. PagerDuty's Service is the routing object: it receives events, owns the escalation policy, and holds the integration keys. In ilert that role belongs to the Alert Source. ilert's Service represents a business capability people subscribe to: it appears on status pages, carries outage history, and can be attached to alert sources and named as an affected service on an incident — but it owns no escalation policy and receives no events. Mapping PD Services onto ilert Services produces a topology that looks right and routes nothing.
A PagerDuty Incident is not an ilert Incident.
PagerDuty's Incident is the actionable page. In ilert that is an Alert
(PENDING → ACCEPTED → RESOLVED), created by an alert source and driven by
an escalation policy. ilert's Incident sits a level above: a coordination
record you declare for a significant event, which links alerts, pages responders,
carries a timeline and an incident channel, and is what Status updates are
posted from. PagerDuty has no single object for it — the closest is a PD incident
after an Incident Workflow has been run against it.
PD incidents therefore map to ilert alerts, one for one. Mapping them onto ilert Incidents instead creates coordination records that no alert source feeds and no escalation policy drives.
Resource mapping
| PagerDuty | ilert | Notes |
|---|---|---|
| Service | Alert Source | Carries escalationPolicy, integrationKey, integrationUrl. PD status is not two-state: active, warning, critical and maintenance all describe a live service — only disabled maps to active: false |
| Integration (routing key) | Alert Source integrationKey / integrationUrl |
New value; every emitter must be re-pointed. A source holds one integrationType and one key, so a PD service with N integrations needs N alert sources |
| Escalation Policy | Escalation Policy | Rules hold escalationTimeout plus users / schedules / teams |
| Schedule | Schedule | type is STATIC or RECURRING |
| Schedule layer | scheduleLayers |
Only on RECURRING schedules; startsOn / endsOn are naive wall-clock (2026-01-01T09:00:00) read against the schedule's timezone — a trailing Z or an offset is rejected, so strip PD's. Shifts and overrides are the opposite and do take an offset |
| Override | Shift, via PUT /schedules/{id}/overrides |
Same Shift payload as a schedule shift, but its own endpoint; must not be in the past |
| Team | Team | visibility is PUBLIC or PRIVATE — only PRIVATE restricts, see below |
| User | User | firstName and lastName are both required; PD's single name may be one token, so pick a filler rather than failing the create |
| Contact method | Contact | Separate objects per channel |
| Notification rule | Notification Preference | Split by priority and by notification type |
| Incident | Alert | |
| Alert (PD's sub-object) | Alert | PD's incident/alert split collapses into one object; grouping is expressed through alertCreation and alertKey instead of a nested layer |
| Business Service | Service | Not only a status-page component: also attached to alert sources (services, autoCreateServices) and to incidents as affected services |
| Status page | Status Page | Page metrics map to Metric + Metric Data Source; see the migrate-from-statuspageio skill for the page-side detail |
| Status update template | Incident Template | sendNotification on the template decides whether subscribers are notified |
| Change Event | Deployment Event + Deployment Pipeline | Separate ingest endpoint and its own integration key — see below |
| Maintenance Window | Maintenance Window | |
| Event Orchestration / Event Rules | Event Flow | A layer above alert sources with its own ingest URL — see below |
| Orchestration dynamic routing | Escalation Policy routingKey + Alert Source routingTemplate |
Direct equivalent; usually replaces the orchestration outright — see below |
| Extension / Webhook | Alert Action (+ Connector) | A connector exists only for named integrations — webhook is an AlertActionType but not a ConnectorType, so a plain webhook is connector-less with the URL in params.webhookUrl. The PD event → triggerTypes mapping is lossy: incident.priority_updated, .status_update_published and .responder.replied have no equivalent — report them rather than dropping them |
| Priority (P1–P5) | Alert severity, integer 1–5 on the event (displayed SEV1–SEV5) |
One for one — see below |
| Urgency (high / low) | Alert priority HIGH / LOW |
Priority stays two-valued; this is the faithful mapping |
| Response Play / Incident Workflow | Incident responders, incident channel, conference bridge — triggered by an ilert incidents Alert Action |
The actions map, and the automatic trigger has an equivalent — see below |
| Postmortem | Postmortem | /incidents/{id}/postmortems — request, edit, delete, and attach external links |
| Live Call Routing | Call Flow + Call Flow Number | Routing targets differ and numbers cannot be ported — see below |
Escalation policy num_loops |
Escalation Policy repeating / frequency |
Both are repeat counts, so this one transfers directly |
Service acknowledgement_timeout |
Alert Action on v-alert-not-resolved |
ACCEPTED stops escalation by design; the reminder moves to an alert action — see below |
Service auto_resolve_timeout |
Alert Source autoResolutionTimeout |
Absent means never |
Service alert_grouping_parameters |
Alert Source alertCreation + alertGroupingWindow |
See below |
| User role | Role / TeamRole |
Fixed enums (ADMIN, USER, RESPONDER, STAKEHOLDER, GUEST), (custom rbac roles require Enterprise plan) |
| Team member | /teams/{id}/members with TeamRole |
|
On-call (/oncalls) |
/on-calls |
Not a migrated object; the endpoint to verify coverage after import |
| Status update on an incident | Status update | Posted from an ilert Incident, via /status-updates |
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.
- 1mo ago Changed a5a41782b1ea
- 1mo ago Changed · +15 lines 537704565c50
- 1mo ago First seen · 490 lines · 16 tokens per session scan B 6b40b5157552
migrate-from-pagerduty is a skill published in the GitHub repository iLert/ilert-cli (12 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 7,913 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
opencli-usage
Discover and invoke OpenCLI capabilities for websites and Chrome. Find commands, inspect schemas, interpret results and choose browser or adapter tools.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
tokf-filter
This skill should be used when the user asks to "create a filter", "write a tokf filter", "add a filter for ", "how do I filter output", or needs guidance on tokf filter step types, templates, pipes, or placement conventions.
antv-x6-editor
A skill for creating and troubleshooting interactive diagrams with AntV X6, a JavaScript engine for editors made of connected nodes and lines. It supports diagram types such as flowcharts, dependency graphs, entity-relationship diagrams, and organization charts.