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.
git clone --depth 1 https://github.com/conallob/o11y-analysis-toolsWrote 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/plugins/conallob/o11y-analysis-tools/promql-cody)<a href="https://agentmods.dev/plugins/conallob/o11y-analysis-tools/promql-cody"><img src="https://agentmods.dev/badge/plugins/conallob/o11y-analysis-tools/promql-cody/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/plugins/conallob/o11y-analysis-tools/promql-cody"><img src="https://agentmods.dev/badge/plugins/conallob/o11y-analysis-tools/promql-cody.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
promql-cody 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 29d 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.
What it actually says
{
"name": "promql-cody",
"source": "./",
"skills": [
"./skills/promql-cody",
"./skills/promql-fmt",
"./skills/label-check",
"./skills/autogen-promql-tests",
"./skills/e2e-alertmanager-test",
"./skills/alert-hysteresis",
"./skills/stale-alerts-analyzer"
],
"description": "Unified agent, plus all six per-tool skills, for the PromQL/Alertmanager CLIs: orchestrates which are hermetic/CI-safe vs. interactive-only and in what order to run them.",
"license": "BSD-3-Clause",
"keywords": [
"promql",
"prometheus",
"alertmanager",
"orchestration",
"formatting",
"labels",
"testing",
"alerting"
],
"strict": false
}What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 405 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#promql-cody in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 29d ago Changed · +10 lines 73d23d1ab490
- 1mo ago First seen · 16 lines scan A c2d333c608a3
promql-cody is a plugin published in the GitHub repository conallob/o11y-analysis-tools (4 stars, last pushed 4d ago), licensed BSD-3-Clause. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
megalinter
Set up, run and fix MegaLinter on any repository: 100+ linters for 69+ languages, 23+ formats and 21+ tooling formats, from CI or locally.
blockwatch
Keep co-dependent code, docs, and config in sync with blockwatch annotations: drift detection (affects), sorted/unique lists, regex/line-count/AI/Lua validation. Includes a skill that teaches agents when and how to add and maintain blocks.
claudeconf
Research-driven, technology-agnostic harness generator for Claude Code: pinned, standard-tool quality + security pipelines (git hooks, CI, e2e, gates, supply-chain admission, agent-hardening) plus a read-only harness-doctor agent.
purist
A single skill that hardens the style checkers and static analyzers already wired into a project: discovers every configuration in place, raises each tool to its strictest practical setting, and adds a list of custom rules on top — it cranks what is configured rather than introducing a new toolchain.
bellwether
Drive PRs to merge-ready: watch CI, fix failures, resolve review comments. Self-contained watch loop that keeps going until pr.ready=true.
costguard
Find and quantify cloud and CI spend waste from your coding agent. Costguard runs read-only billing checks (GitHub Actions, Supabase, Railway, Netlify, Neon), static CI/cron waste rules, dry-run-first auto-fixes for workflow files, and a monthly cost digest — all driven from your session via /costguard-audit…