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/tahirraufkeeyu/software-development-agent-stack--sdas/monitoring-setupnpx skills add tahirraufkeeyu/software-development-agent-stack--sdas --skill monitoring-setupgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/skills/tahirraufkeeyu/software-development-agent-stack--sdas/monitoring-setup)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/monitoring-setup"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/monitoring-setup.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.00076 | $0.02961 |
| Opus 5 | $0.00038 | $0.01481 |
| Sonnet 5 | $0.00015 | $0.00592 |
| Haiku 4.5 | $0.00008 | $0.00296 |
Grade A, and why
monitoring-setup 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 6d 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.
- `kubectl` (≥ 1.27), `helm` (≥ 3.12), `jq`, `yq`, `curl`. How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User says "set up monitoring", "install Prometheus", "add Grafana dashboards", "wire Alertmanager to Slack", or "we need alerts for CPU/memory/error rate".
- A new cluster has no metrics backend and services are emitting
/metricsendpoints that nothing is scraping. - Existing Prometheus is present but ServiceMonitors are missing for a specific workload.
- User wants Golden Signal coverage (latency, traffic, errors, saturation) on an existing service.
Do not use this skill for log aggregation (use log-aggregation), for tracing (out of scope — install Tempo/Jaeger separately), or for synthetic monitoring (use blackbox-exporter which this skill can point at).
Inputs
- Kubeconfig context for the target cluster (
kubectl config current-context). - Target namespace (default
monitoring). - Helm chart version of
kube-prometheus-stack(default: pin to a known-good release, e.g.55.5.0+). - Notification targets: Slack webhook URL (per severity channel) and/or PagerDuty integration key.
- List of services to cover with ServiceMonitors (namespace, label selector, port name, metrics path).
- Storage class for Prometheus PVC and retention window (default
30d).
Outputs
- Running
kube-prometheus-stackrelease in the target namespace with Prometheus, Grafana, Alertmanager, node-exporter, kube-state-metrics, Prometheus Operator. ServiceMonitorresources for every listed service.PrometheusRulewith the baseline alerts from references/alertmanager-rules-template.yaml.- Grafana dashboards imported from references/grafana-dashboard-templates.json, plus the community dashboards for kubelet (1860), node-exporter (1860), and kube-state-metrics (13332).
- Alertmanager configuration with per-severity routing (
critical→ PagerDuty + Slack,warning→ Slack only,info→ swallowed). - A verification report:
prom-rules.yamllint result, list of up targets, a test alert firing end-to-end.
What ships with it
2 files beside SKILL.md 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.
- 6d ago First seen · 218 lines · 76 tokens per session scan A d265c4d0e1bb
monitoring-setup is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 2,961 once invoked, about $0.0004 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 skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…