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.
/plugin marketplace add conallob/o11y-analysis-toolsnpx agentmods add plugins/conallob/o11y-analysis-tools/promql-codygit 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.svg" alt="Measured on agentmods" 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 yesterday.
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"
],
"description": "Unified agent: orchestrates all six PromQL/Alertmanager CLIs together, deciding which are hermetic/CI-safe vs. interactive-only and in what order to run them.",
"license": "BSD-3-Clause",
"keywords": [
"promql",
"prometheus",
"alertmanager",
"orchestration"
],
"strict": false
}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.
- yesterday 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 1mo 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
Recursive Test
Bundle that ships skills, agents, commands, hooks and an MCP config; used to test recursive sub-tree load.
Acme Extras
Bundle that ships hooks and an MCP config.
bellwether
Drive PRs to merge-ready: watch CI, fix failures, resolve review comments. Self-contained watch loop that keeps going until pr.ready=true.
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.
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…
jenkins-cli
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.