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 alibaba-iac-and-deploymentgit 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/alibaba-iac-and-deployment)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/alibaba-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/alibaba-iac-and-deployment/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/alibaba-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/alibaba-iac-and-deployment.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.00095 | $0.02815 |
| Opus 5 | $0.00048 | $0.01407 |
| Sonnet 5 | $0.00019 | $0.00563 |
| Haiku 4.5 | $0.00010 | $0.00281 |
Grade A, and why
alibaba-iac-and-deployment 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alibaba IaC and Deployment
When to use
- Greenfield project — picking an IaC tool for Alibaba Cloud.
- Inheriting console-built infrastructure that needs to come into code.
- Designing a CI/CD pipeline for application and infrastructure deployment.
- Hardening a release for safe rollout and rollback.
- Reviewing an existing IaC repo for drift, secret leakage, or state hygiene.
- Wiring RAM Role OIDC authentication for GitHub Actions or Jenkins.
IaC tool — picking one
| Tool | Pick when |
|---|---|
Terraform (aliyun/alicloud) |
Primary recommendation. Multi-cloud or multi-provider (Cloudflare + GitHub + Alibaba), or a single IaC standard across the org. Largest community; best module ecosystem; aliyun/alicloud provider ≥ 1.220 has comprehensive coverage. |
| ROS (Resource Orchestration Service) | Team already standardized on ROS; China-region tooling constraints; you need native Alibaba console integration; or you are shipping templates inside Alibaba Cloud Marketplace. Syntax is similar to CloudFormation. |
| Pulumi | Team strongly prefers a real programming language (Go, Python, TypeScript) and alicloud Pulumi provider suits the workload. Niche but viable. |
| Alibaba Cloud CLI + scripts | Bootstrap-only steps (account root hardening, KMS key creation, first Terraform state bucket) where IaC would be circular. |
Terraform is the default. ROS is acceptable when Alibaba ecosystem tooling (DataWorks, ACK console integration, commercial marketplace) makes it the better fit. Avoid mixing tools for the same resource layer — Terraform for foundations and ROS for app stacks is fine; Terraform managing a resource while ROS re-provisions it is not.
Alibaba Cloud CLI
- Version:
aliyun≥ 3.0.230. Install via the official installer orbrew install aliyun-clion macOS. - Authentication: configure a named profile with a RAM Role + STS assumption, not a root AK/SK.
aliyun configure --mode RamRoleArn --profile prod \ --region cn-hangzhou \ --ram-role-arn acs:ram::123456789:role/deploy-role \ --ram-session-name ci-session - Output format:
--output jsonin scripts for deterministic parsing;--output tablefor humans. - Pagination: use
--page-sizeand loop on--page-number; many list APIs page at 10–50 by default. - Dry-run mode:
--dry-runon mutating commands where supported; not available for all APIs — verify before relying on it.
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 · 197 lines · 95 tokens per session scan A c1bca449e4f5
alibaba-iac-and-deployment is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 95 tokens to every session and 2,815 once invoked, about $0.0005 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…