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 skills add jsgerman-oss/blackrim-nimbus-skills --skill aws-observability-and-costgit clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-skillsWrote 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/jsgerman-oss/blackrim-nimbus-skills/aws-observability-and-cost)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/aws-observability-and-cost"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/aws-observability-and-cost/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/aws-observability-and-cost"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/aws-observability-and-cost.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01501 |
| Opus 5 | $0.00030 | $0.00750 |
| Sonnet 5 | $0.00012 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
aws-observability-and-cost 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Observability and Cost
When to use
- Setting up logs / metrics / traces for a new service.
- Building an SLO dashboard or wiring an alarm to oncall.
- Diagnosing a latency / error / cost regression.
- Negotiating a Savings Plan or Reserved Instance commitment.
- Sizing a quarterly cloud cost review.
Observability pillars
| Pillar | Service |
|---|---|
| Metrics | CloudWatch Metrics + Container Insights + Lambda Insights |
| Logs | CloudWatch Logs (with Logs Insights), or OpenSearch / S3 + Athena for long retention |
| Traces | X-Ray (AWS-native) or OpenTelemetry → AWS Distro for OpenTelemetry (ADOT) |
| Synthetics | CloudWatch Synthetics (canaries) |
| Real User Monitoring | CloudWatch RUM |
| Service map | X-Ray Service Map / CloudWatch ServiceLens |
Defaults — every service
- Structured JSON logs with a stable request-id field.
- Embedded Metric Format (EMF) for app-level metrics — emit from logs, cheaper than
PutMetricData. - Tracing on (X-Ray or OTEL), with the request-id propagated as a trace baggage / annotation.
- At least one alarm per service tied to user pain (error rate, p99 latency, queue age, dead-letter count). Never alarm on "CPU > 80%" alone.
- Log retention: 30 d for app logs in CloudWatch; ship to S3 + Athena for longer if regulated. Default infinite retention is an unbounded bill.
Alarms — write them like contracts
Good alarm spec:
- Signal: which metric, at which percentile, over which window.
- Threshold: the number that means "human attention needed".
- Action: which SNS topic / EventBridge rule / PagerDuty integration.
- Runbook: linked in the alarm description — first thing the responder reads.
Bad alarms: floating thresholds, "CPU > 80%", anything that fires more than once a week without action.
For composite signals, use CloudWatch composite alarms (AND/OR over child alarms) to suppress noise.
Dashboards
- One per service, one per environment.
- Top row: SLI metrics (availability, latency, error rate). Below: dependencies (upstream latency, downstream error rate). Below that: capacity (memory, queue depth, db connections).
- Variables (regions, env) for dashboards reused across deployments.
- Generated from IaC so they survive account moves.
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.
- 12d ago First seen · 128 lines · 61 tokens per session scan A fcda7e4bafa6
aws-observability-and-cost is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 61 tokens to every session and 1,501 once invoked, about $0.0003 per session on Opus 5. 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-08-31.
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-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).
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…
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…