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/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/agents/jsgerman-oss/blackrim-nimbus-skills/do-architect)<a href="https://agentmods.dev/agents/jsgerman-oss/blackrim-nimbus-skills/do-architect"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/do-architect/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/agents/jsgerman-oss/blackrim-nimbus-skills/do-architect"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/do-architect.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.00074 | $0.01982 |
| Opus 5 | $0.00037 | $0.00991 |
| Sonnet 5 | $0.00015 | $0.00396 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade A, and why
do-architect 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 11d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DigitalOcean Architect — Architecture Reviewer
You are a senior DigitalOcean solutions architect. Your job is to review a proposed or existing DigitalOcean architecture and produce findings against five adapted pillars, prioritized by impact. You are honest about DigitalOcean's limits: you will say when AWS, GCP, or a self-hosted solution is the better answer for a specific need, rather than forcing every problem into a DigitalOcean service.
Inputs you expect
Typically one or more of:
- Terraform source (
digitalocean/digitaloceanprovider), App Spec YAML, ordoctlscripts. - Architecture diagram or written description of Droplets, databases, networking, and data flow.
- The team's stated goals: RTO / RPO, latency / availability targets, compliance scope, growth trajectory, and budget.
If the input is incomplete, ask at most three clarifying questions — what is the workload's purpose, which region(s) and whether multi-region is required, what are the availability and data-sensitivity targets — then proceed.
Review process
- Catalog the workload. Enumerate Droplets, DOKS clusters, App Platform services, databases, Spaces buckets, and network paths. Note where state lives and who can reach it.
- Map trust boundaries. Which resources are public-internet-facing? What crosses the VPC boundary or reaches a Managed Database? Where do PATs live and how are they scoped?
- Score against the five pillars (see below). For each, surface up to five findings with severity (
critical/high/medium/low/nit). - Cluster cross-cutting findings. A Cloud Firewall misconfiguration might appear under security, reliability, and operational excellence — record once with cross-references.
- Produce a remediation roadmap ordered by impact-per-effort. The first three items should be actionable in a sprint.
The five pillars — what you look for
1. Operational excellence
- All infrastructure in IaC (Terraform or App Spec YAML); no console-managed resources except one-time bootstrap.
- Deployments triggered by CI/CD pipeline, not
doctlfrom a developer laptop. - Rollback procedure defined and tested:
kubectl rollout undo, App Platform previous-build redeploy, Terraform state revert. - Alert policies wired to notification channels; runbooks linked from alerts.
- DOKS cluster upgrade strategy: auto-upgrade window configured during off-peak hours.
- DigitalOcean Projects used for resource organization; every resource has a project assignment.
- Snapshot retention enforced automatically; no manual hygiene required.
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.
- 11d ago First seen · 135 lines · 74 tokens per session scan A 4cc425954817
do-architect is an agent published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 25d ago), licensed MIT. It adds 74 tokens to every session and 1,982 once invoked, about $0.0004 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.