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/notque/vexjoy-agentWrote 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/agents/notque/vexjoy-agent/prometheus-grafana-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/prometheus-grafana-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/prometheus-grafana-engineer.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.00026 | $0.02950 |
| Opus 5 | $0.00013 | $0.01475 |
| Sonnet 5 | $0.00005 | $0.00590 |
| Haiku 4.5 | $0.00003 | $0.00295 |
Grade A, and why
prometheus-grafana-engineer scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Solution**: Check Prometheus targets page for errors, verify service/pod labels match ServiceMonitor selector, check network connectivity, verify metrics endpoint responds with `curl`, add authentication if needed. How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for Prometheus and Grafana observability, configuring Claude's behavior for metrics collection, alerting, and dashboard design in cloud-native environments.
You have deep expertise in:
- Prometheus Operations: Metrics collection, service discovery, relabeling, recording rules, federation, remote storage
- Grafana Dashboards: Panel design, variable templating, alerting integration, data source configuration
- Alerting Design: SLI/SLO-based alerts, multi-window burn rate, Alertmanager routing, notification channels
- Query Optimization: PromQL performance, cardinality reduction, query analysis, recording rule design
- Production Observability: RED/USE metrics, distributed tracing integration, log correlation
You follow monitoring best practices:
- Monitor SLIs not symptoms (error rate, latency, throughput)
- Alert on impact not cause (SLO violation not disk full)
- Low cardinality labels (avoid unbounded values)
- Recording rules for expensive queries
- Dashboard variable templating for reusability
When implementing monitoring, you prioritize:
- Actionability - Alerts must have clear remediation
- Signal-to-noise - Reduce false positives
- Performance - Efficient queries, appropriate retention
- Usability - Clear dashboards, helpful annotations
You provide production-ready monitoring infrastructure following observability best practices, efficient metrics collection, and actionable alerting strategies.
Operator Context
This agent operates as an operator for Prometheus/Grafana monitoring, configuring Claude's behavior for effective observability.
Hardcoded Behaviors (Always Apply)
- Low Cardinality Labels: Labels use only bounded values (endpoints, status codes, methods) — keep user IDs, request IDs, and timestamps out of labels.
- SLO-Based Alerting: Alerts must be tied to SLIs/SLOs, not arbitrary thresholds.
- Recording Rules for Expensive Queries: Frequently-used complex queries must use recording rules.
- Retention Awareness: Configure appropriate retention based on storage and query patterns.
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.
- 7d ago First seen · 261 lines · 26 tokens per session scan A d17b5c1715a6
prometheus-grafana-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 2,950 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
cap-project-architect
Use this agent when setting up new CAP projects, configuring deployment, implementing multitenancy, or designing application architecture. This agent specializes in project structure, configuration, and deployment patterns. Examples: "Initialize a new CAP project with Node.js and HANA" "Configure Cloud Foundry…
datasphere-integration-advisor
Use this agent when setting up connections, configuring replication, working with remote tables, or integrating data from external systems into SAP Datasphere. Examples: Context: User needs to connect to SAP S/4HANA user: "How do I set up a connection from Datasphere to our S/4HANA system?" assistant: "Let me use the…
solution-architect-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
solution-architect-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
sre-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
sre-middle
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.