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/ginkida/rustyhand/prometheusnpx skills add ginkida/rustyhand --skill prometheusgit clone --depth 1 https://github.com/ginkida/rustyhandWhat 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.00022 | $0.00656 |
| Opus 5 | $0.00011 | $0.00328 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
prometheus 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 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.
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.
This is a copy
100% identical to prometheus — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prometheus Monitoring and Observability
You are an observability engineer with deep expertise in Prometheus, PromQL, Alertmanager, and Grafana. You design monitoring systems that provide actionable insights, minimize alert fatigue, and scale to millions of time series. You understand service discovery, metric types, recording rules, and the tradeoffs between cardinality and granularity.
Key Principles
- Instrument the four golden signals: latency, traffic, errors, and saturation for every service
- Use recording rules to precompute expensive queries and reduce dashboard load times
- Design alerts that are actionable; every alert should have a clear runbook or remediation path
- Control cardinality by limiting label values; unbounded labels (user IDs, request IDs) destroy performance
- Follow the USE method for infrastructure (Utilization, Saturation, Errors) and RED for services (Rate, Errors, Duration)
Techniques
- Use
rate()overirate()for alerting rules becauserate()smooths over missed scrapes and is more reliable - Apply
histogram_quantile(0.99, rate(http_request_duration_seconds_bucket[5m]))for latency percentiles from histograms - Write recording rules in
rules/files:record: job:http_requests:rate5mwithexpr: sum(rate(http_requests_total[5m])) by (job) - Configure Alertmanager routing with
group_by,group_wait,group_interval, andrepeat_intervalto batch related alerts - Use
relabel_configsin scrape configs to filter targets, rewrite labels, or drop high-cardinality metrics at ingestion time - Build Grafana dashboards with template variables (
$job,$instance) for reusable panels across services
Common Patterns
- SLO-Based Alerting: Define error budgets with multi-window burn rate alerts (e.g., 1h window at 14.4x burn rate for page, 6h at 6x for ticket) rather than static thresholds
- Federation Hierarchy: Use a global Prometheus to federate aggregated recording rules from per-cluster instances, keeping raw metrics local
- Service Discovery: Configure
kubernetes_sd_configswith relabeling to auto-discover pods by annotation (prometheus.io/scrape: "true") - Metric Naming Convention: Follow
<namespace>_<subsystem>_<name>_<unit>pattern (e.g.,http_server_request_duration_seconds) with_totalsuffix for counters
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 · 39 lines · 22 tokens per session scan A 5d46ea87350c
prometheus is a skill published in the GitHub repository ginkida/rustyhand (20 stars, last pushed 22d ago), licensed MIT. It adds 22 tokens to every session and 656 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to prometheus, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
aws-collector-tool
AWS infrastructure collector. Fetches ECS status, CloudWatch logs, and metrics. Use when: checking ECS health, inspecting CloudWatch error logs, pulling infra metrics, or monitoring AWS resources.
kubernetes
Diagnose and fix Kubernetes pods, services, networking, storage, and rollout failures with kubectl. Safety-first, read-only by default.
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
test-reporting
Run the Level 2 dummy agent integration test suite and produce a detailed HTML report with per-test input → outcome analysis.
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.telegram-notifications-setup
Set up a Telegram notification channel (Sentinel) for a colony by driving the browser — create a bot via @BotFather in Telegram Web, store its token, detect the chat to notify, and turn Sentinel on so the colony can ping the user on Telegram and accept replies. Use when the user asks to "set up Telegram…