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 ilert-essentialsgit 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/ilert-essentials)<a href="https://agentmods.dev/skills/ilert/ilert-cli/ilert-essentials"><img src="https://agentmods.dev/badge/skills/ilert/ilert-cli/ilert-essentials/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/ilert-essentials"><img src="https://agentmods.dev/badge/skills/ilert/ilert-cli/ilert-essentials.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.00000 | $0.04317 |
| Opus 5.5 | $0.00000 | $0.01727 |
| Sonnet 5.5 | $0.00000 | $0.00863 |
| Haiku 4.5 | $0.00000 | $0.00432 |
Grade A, and why
ilert-essentials 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 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.
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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ilert essentials
ilert skills list is the index of everything else — including the
migrate-from-* playbooks. Migrating an existing setup? Read this first, then
the relevant one: they cover the mapping, this covers the platform.
The object model in one pass
| Object | What it is |
|---|---|
| Event | What monitoring tools send. integrationKey routes it to an alert source |
| Alert Source | Receives events. Owns the escalationPolicy, the integrationKey / integrationUrl, and every parsing and grouping setting |
| Alert | The actionable thing: PENDING → ACCEPTED → RESOLVED, created by an alert source, driven by an escalation policy, triggers notifications to responders |
| Service | A business capability people subscribe to. Appears on status pages, carries outage history, is attached to sources and named on incidents. Owns no policy and receives no events |
| Incident | The coordination record above alerts (used on business impact) — multi channel responders, timeline, incident channel. It publishes nothing by itself |
| Status update | The public message posted from an incident. This is what reaches status pages and subscribers |
| Escalation Policy | Ordered rules with escalationTimeout, targeting users, schedules or teams. Also repeating / frequency, delayMin, routingKey |
| Schedule | STATIC or RECURRING; RECURRING carries scheduleLayers (at least one), and resolves to one person on call — where layers overlap the higher one wins. Overrides go through PUT /schedules/{id}/overrides |
| Event Flow | A routing layer above alert sources with its own ingest URL. Nodes: ROOT, DEFINE_BRANCHES, ROUTE_EVENT, SUPPORT_HOURS, WAIT, TRANSFORM |
| Call Flow | The same idea for inbound phone calls: IVR_MENU, AUDIO_MESSAGE, SUPPORT_HOURS, ROUTE_CALL, PARALLEL_ROUTE_CALL, VOICEMAIL, PIN_CODE, CREATE_ALERT, BLOCK_NUMBERS, AGENTIC |
| Alert Action + Connector | Outbound automation. The Connector holds credentials, the Alert Action binds it to a source with triggerMode, triggerTypes and ICL conditions |
| Maintenance Window | Takes both services and alertSources — communication and suppression in one object |
| Deployment Pipeline / Event | Deploy traffic, on its own ingest endpoint and its own integration key. Not alert traffic |
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 · +8 lines bbda624104dc
- 1mo ago First seen · 279 lines · 0 tokens per session scan A 9b9fb68e2a35
ilert-essentials is a skill published in the GitHub repository iLert/ilert-cli (12 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,317 tokens. 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
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.