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/autogen-promql-testsWrote 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/autogen-promql-tests)<a href="https://agentmods.dev/skills/conallob/o11y-analysis-tools/autogen-promql-tests"><img src="https://agentmods.dev/badge/skills/conallob/o11y-analysis-tools/autogen-promql-tests/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/conallob/o11y-analysis-tools/autogen-promql-tests"><img src="https://agentmods.dev/badge/skills/conallob/o11y-analysis-tools/autogen-promql-tests.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.01288 |
| Opus 5 | $0.00000 | $0.00644 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
autogen-promql-tests 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 10d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autogen-promql-tests
Coverage auditor and test-skeleton generator for Prometheus rule files. It
does not know your actual metric shapes — it emits a promtool-compatible
test file full of TODO placeholders that a human (or an agent that has
read the real metrics) must fill in with realistic input series and
expected values. Hermetic — no network access.
When to use this skill
- A rules file has alerts or recording rules with no corresponding
promtool test rulescoverage, and you want a starting skeleton rather than writinginput_series/exp_alertsblocks from scratch. - You want a quick coverage report: how many of N rules currently have tests, and which ones don't.
- This is a bootstrap tool, best run interactively the first time a
rule is added — not a CI gate, since its generated output is
intentionally incomplete (
TODOmarkers) and would failpromtool test rulesuntil a human fills them in.
Setup
go build -o bin/autogen-promql-tests ./cmd/autogen-promql-tests
# or: go install github.com/conallob/o11y-analysis-tools/cmd/autogen-promql-tests@latest
Usage
autogen-promql-tests [options]
| Flag | Default | Effect |
|---|---|---|
--rules |
(required) | Path to the Prometheus rules YAML file to audit. |
--tests |
"" |
Path to an existing test file to check coverage against. If omitted, the tool auto-discovers <rules-basename>_test.yml next to the rules file. |
--fix |
false |
Generate a test file covering the untested alerts/rules. |
--verbose |
false |
Print discovery/loading detail. |
Typical invocations
# Coverage report only (exit 1 if anything is untested)
autogen-promql-tests --rules=./alerts.yml
# Generate a test skeleton for whatever's untested
autogen-promql-tests --rules=./alerts.yml --fix
# Check against an explicit, non-default-named test file
autogen-promql-tests --rules=./rules.yml --tests=./custom_tests.yml
Without --tests, it looks for <rules>_test.yml (rules file's basename
with .yml/.yaml stripped, _test.yml appended) in the same directory.
With --fix, the same path is the default write target unless --tests
is also given, in which case that path is used both to read and write.
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.
- 10d ago First seen · 124 lines · 0 tokens per session scan A 9b6dbacceb1f
autogen-promql-tests is a skill published in the GitHub repository conallob/o11y-analysis-tools (4 stars, last pushed 1mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,288 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
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
squad-conventions
Core conventions and patterns used in the Squad codebase.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.