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/nerds-odd-e/doughnut/cloud-vm-setupnpx skills add nerds-odd-e/doughnut --skill cloud-vm-setupgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWhat 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.00064 | $0.00832 |
| Opus 5 | $0.00032 | $0.00416 |
| Sonnet 5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
cloud-vm-setup 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.
What it actually says
Purpose: Cloud-agent development and testing when nix develop is unavailable.
Output: Environment ready for tests + summary ending with ## CLOUD VM READY.
Pre-configured: Node.js v24.16.0, pnpm 11.3.0 — no nix needed.
Ports:
| Service | Port |
|---|---|
| Spring Boot | 9081 |
| Local LB | 5173 |
| Vite dev | 5174 |
| MySQL | 3309 |
| Redis | 6380 |
CI=1 is exported by the setup script (CLI PTY tests use pipe fallback, matching
GitHub Actions).
source /workspace/scripts/cloud_agent_setup.sh
Installs: Java 25, MySQL 8.4 (port 3309), Redis (port 6380), xvfb, and initializes test databases.
Single file: pnpm -C frontend test tests/path/to/TestFile.spec.ts (no -- before the path).
<success_criteria>
- Setup script run when backend/E2E needed
- Commands run without nix prefix
- Correct ports and healthcheck commands available
- Final output includes
## CLOUD VM READY</success_criteria>
Common commands:
| Task | Command |
|---|---|
| Frontend tests | pnpm frontend:test |
| Backend tests | pnpm backend:verify |
| Linting | pnpm lint:all |
| Formatting | pnpm format:all |
## CLOUD VM READY
<out_of_scope>
- Do not use
CURSOR_DEV=true nix develop -con Cloud VM. - Do not assume local Nix shell ports or paths (
/Users/...vs/workspace/...). </out_of_scope>
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 · 111 lines · 64 tokens per session scan A 0df5e42d25f4
cloud-vm-setup is a skill published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 832 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-30.
Other skills, from other repositories
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
huggingface-spaces
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't…
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…
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.