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 agentmods add skills/abdullahkhawer/devops-skills/prometheus-clinpx skills add abdullahkhawer/devops-skills --skill prometheus-cligit clone --depth 1 https://github.com/abdullahkhawer/devops-skillsWhat 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 | $0.00033 | $0.01288 |
| Opus 5 | $0.00016 | $0.00644 |
| Sonnet 5 | $0.00007 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade B, and why
prometheus-cli scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
mkdir -p ~/.prometheus && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Query Prometheus metrics using the HTTP API via curl. Use for instant queries, range queries, metadata lookups, and alert/rule inspection. How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prometheus CLI Skill
Use the instance and rules below when constructing all Prometheus API commands.
Instances
Update the table below with your Prometheus instance URLs before using this skill:
| Environment | Base URL | Token File |
|---|---|---|
| Production | https://<your-prometheus-prod-url> |
~/.prometheus/prod.token |
| Staging | https://<your-prometheus-staging-url> |
~/.prometheus/staging.token |
If the target instance is unclear, ask the user before running any command.
Prerequisites (one-time setup by user)
Obtain a Prometheus API token for each instance you intend to use and save it to the corresponding token file (see instance table above). Never print or display token values. Do not perform these steps yourself.
For each instance:
- Obtain an API token (via your team or the monitoring platform)
- Save it:
mkdir -p ~/.prometheus && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE>
Command Format
All API calls use curl with the token read from the instance's token file (see instance table above):
curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
"<BASE_URL>/api/v1/<endpoint>" | jq .
Example (production):
curl -s -H "Authorization: Bearer $(cat ~/.prometheus/prod.token)" \
"https://<your-prometheus-prod-url>/api/v1/query?query=up" | jq .
Available API Endpoints
Read-only (safe, no confirmation needed)
| Endpoint | Description |
|---|---|
/api/v1/query?query=<expr> |
Instant query — evaluate a PromQL expression at current time |
/api/v1/query_range?query=<expr>&start=<ts>&end=<ts>&step=<dur> |
Range query — evaluate PromQL over a time range |
/api/v1/labels |
List all label names |
/api/v1/label/<name>/values |
List values for a specific label |
/api/v1/series?match[]=<selector> |
Find time series matching a selector |
/api/v1/metadata |
List metric metadata (type, help text) |
/api/v1/rules |
List all recording and alerting rules |
/api/v1/alerts |
List currently firing alerts |
/api/v1/targets |
List scrape targets and their health |
/api/v1/targets/metadata |
List metadata for scraped targets |
/api/v1/status/config |
Show current Prometheus configuration |
/api/v1/status/flags |
Show runtime flags |
/api/v1/status/runtimeinfo |
Show runtime information |
/api/v1/status/buildinfo |
Show build information |
/api/v1/status/tsdb |
Show TSDB stats |
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.
- 2d ago First seen · 111 lines · 33 tokens per session scan B 859d2c25384c
prometheus-cli is a skill published in the GitHub repository abdullahkhawer/devops-skills (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,288 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
temps-platform-setup
Safely verify and configure an existing Temps platform installation. Use when the user wants to inspect installation readiness, connect the installed CLI, perform initial configuration, manage platform users, or configure DNS and TLS without exposing credentials or executing unverified remote code.
add-custom-domain
Add a custom domain to a Temps project and provision an automatic SSL/TLS certificate via Let's Encrypt, driven entirely from the @temps-sdk/cli CLI. Handles subdomains, apex domains, HTTP-01 and DNS-01 challenges, and wildcard domains. Use when the user wants to: (1) Add a custom domain to their Temps app, (2) Set up…
context-manage
Manage Kurtosis contexts for connecting to different Kurtosis instances. Add, list, switch, and remove contexts. Use when working with multiple Kurtosis environments (local, remote, team shared).
gateway
Start and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.