Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/conallob/o11y-analysis-toolsnpx agentmods add skills/conallob/o11y-analysis-tools/e2e-alertmanager-testWrote 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/conallob/o11y-analysis-tools/e2e-alertmanager-test)<a href="https://agentmods.dev/skills/conallob/o11y-analysis-tools/e2e-alertmanager-test"><img src="https://agentmods.dev/badge/skills/conallob/o11y-analysis-tools/e2e-alertmanager-test.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.00153 | $0.01918 |
| Opus 5 | $0.00077 | $0.00959 |
| Sonnet 5 | $0.00031 | $0.00384 |
| Haiku 4.5 | $0.00015 | $0.00192 |
Grade A, and why
e2e-alertmanager-test 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 8d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
e2e-alertmanager-test
Takes the exp_alerts fixtures out of a Prometheus promtool-style unit
test file, POSTs each one to a real Alertmanager's /api/v2/alerts
endpoint, and renders what the resulting notification would look like in
several formats. It does not test routing/inhibition logic inside this
tool itself — it exercises whatever routing your target Alertmanager
instance is actually configured with, and shows you the rendered output.
When to use this skill
- Before merging an alert change, to see the actual notification content (subject line, body, Slack attachment) a human on-call would receive — not just "does it fire," but "does it read well."
- As a CI step against a throwaway/ephemeral Alertmanager container, producing a rendered-output artifact that reviewers can diff between runs, the same way a UI snapshot test is diffed. Fed a skeleton config (see below), this run is fully hermetic — see Achieving full hermeticity in CI.
- This tool's own external dependency is the Alertmanager instance, not
historical data — unlike
alert-hysteresis/stale-alerts-analyzer, it needs no real production history, so a fresh, disposable Alertmanager instance is sufficient and the run is fully reproducible.
Prerequisites
- A Prometheus unit-test file with
exp_alertsfixtures — typically the output ofautogen-promql-tests(see that skill) with real, filled-in labels/annotations, or a hand-writtenpromtooltest file. Test cases whoseexp_alertsis empty (asserting "does not fire") are silently skipped — there's nothing to render for those. - A running Alertmanager reachable over HTTP, defaulting to
http://localhost:9093. For CI or local preview, run one disposably:docker run -d -p 9093:9093 prom/alertmanager
Achieving full hermeticity in CI
The e2e-alertmanager-test binary itself is never hermetic on its own —
it always needs to POST to a real, reachable Alertmanager. But the
routing config that Alertmanager instance loads is entirely under your
control, and that's where every external dependency can be removed:
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.
- 8d ago First seen · 159 lines · 153 tokens per session scan A 744c3d0054f0
e2e-alertmanager-test is a skill published in the GitHub repository conallob/o11y-analysis-tools (4 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 153 tokens to every session and 1,918 once invoked, about $0.0008 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
BrowserStack Cloud Testing
Cloud-based cross-browser and cross-device testing with BrowserStack including Automate, App Automate, Percy visual testing, Observability, and integration with Playwright, Selenium, and CI/CD pipelines.
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
e2e-testing
Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable locators, web-first assertions, storageState auth, trace/retries, and flakes that only bite in CI. NOT in-process component tests (that is testing-web), NOT WCAG auditing (that is accessibility), NOT the…
Browser Smoke Testing
Open a local web target and verify that the main page renders and core controls respond.