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-opsgeniegit 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-opsgenie)<a href="https://agentmods.dev/skills/ilert/ilert-cli/migrate-from-opsgenie"><img src="https://agentmods.dev/badge/skills/ilert/ilert-cli/migrate-from-opsgenie/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-opsgenie"><img src="https://agentmods.dev/badge/skills/ilert/ilert-cli/migrate-from-opsgenie.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.00017 | $0.08113 |
| Opus 5.5 | $0.00007 | $0.03245 |
| Sonnet 5.5 | $0.00003 | $0.01623 |
| Haiku 4.5 | $0.00002 | $0.00811 |
Grade B, and why
migrate-from-opsgenie 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: GenieKey $OPSGENIE_API_KEY" # the shell expands this first How it starts
The opening of the file, as written. The whole thing — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating from Opsgenie to ilert
The hard part is not the object mapping — it is that the two products route alerts through different objects. Opsgenie routes team-first; ilert routes source-first. A simple setup maps one-to-one, but any configuration that leaned on team routing rules routes differently after a faithful field-by-field import.
For ilert's own semantics and the CLI behaviour behind a bulk import, read the
ilert-essentials skill alongside this one. Where Opsgenie's own data lives — and
how to hold a foreign API key while you read it — is under Reading the Opsgenie
side below; start there when the job is extraction rather than design.
The routing model difference
In Opsgenie an integration hands an alert to a team, and the team's routing rules decide which escalation applies, with alert/notification policies filtering along the way.
In ilert the Alert Source owns the escalation policy directly. There is no object equivalent to a team routing rule, but two mechanisms between them absorb almost every routing rule you will find, and they are where to look first:
-
Routing keys — when the emitter can name the branch it wants. An Escalation Policy carries a
routingKey. An event supplying a matching key overrides the alert source's own policy. Keys are comma-separated and evaluated left to right, falling back to the source's policy when none match, and the key can be pulled from the payload with the alert source'sroutingTemplate. One alert source, several escalation paths, no extra objects. -
Event Flows — for everything else. This is the general answer whenever an Opsgenie rule has no direct equivalent in an alert source setting. An Event Flow is a routing layer that sits above alert sources rather than beside them: it has its own
integrationKey/integrationUrl, so emitters post to the flow instead of to a source, as a drop-in replacement for a source URL at the sender. Inside it is a tree of nodes:
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 · -1 lines 6db2ed4e71bb
- 1mo ago Changed · +20 lines 00683f574baf
- 1mo ago First seen · 497 lines · 17 tokens per session scan B ecf1c4213993
migrate-from-opsgenie is a skill published in the GitHub repository iLert/ilert-cli (12 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 8,113 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.