cloudgov-deploy

cloudgov-deploy is a skill for Claude Code, Codex from GSA-TTS/agentic-coding-playbook. It costs 20 tokens per session (1,497 once invoked), scanned B, original, CC0-1.0.

A deployment workflow for cloud.gov, a government cloud platform for hosting applications. It covers sandbox setup, deployment configuration, and continuous integration and delivery pipelines.

In plain words
What is it for?
Setting up a cloud.gov sandbox, generating deployment manifests, configuring CI/CD, and deploying an application with the Cloud Foundry command-line tool.
Why use it?
It gives federal teams a defined path from a local application to a hosted cloud.gov deployment without managing servers directly.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/gsa-tts/agentic-coding-playbook/cloudgov-deploy
Any agent
npx skills add GSA-TTS/agentic-coding-playbook --skill cloudgov-deploy
Clone the repo
git clone --depth 1 https://github.com/GSA-TTS/agentic-coding-playbook

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cloudgov-deploy

README.md
[![agentmods](https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/cloudgov-deploy.svg)](https://agentmods.dev/skills/gsa-tts/agentic-coding-playbook/cloudgov-deploy)
Your own site
<a href="https://agentmods.dev/skills/gsa-tts/agentic-coding-playbook/cloudgov-deploy"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/cloudgov-deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,497 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.01497
Opus 5 $0.00010 $0.00749
Sonnet 5 $0.00004 $0.00299
Haiku 4.5 $0.00002 $0.00150

Measured 4d ago against content hash 42c67191ba27, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

cloudgov-deploy scanned grade B with 2 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 4d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo mv cf8 /usr/local/bin/cf

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl https://<project-name>.app.cloud.gov/
.agents/skills/cloudgov-deploy/SKILL.md · 223 lines

How it starts

The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: cloud.gov Deployment

Deploy a federal application to cloud.gov — the FedRAMP-authorized platform available to all federal employees.

When to Use

  • Deploying any federal application
  • User says "deploy to cloud.gov" or "push to sandbox"
  • PROJECT_PLAN.md lists cloud.gov as the hosting platform

Why cloud.gov

  • Free sandbox for anyone with a .gov, .mil, or .fed.us email
  • FedRAMP Authorized — inherits ~80% of NIST 800-53 controls
  • Zero infrastructure management — no servers, no patches, no OS updates
  • cf push deploys in minutes — no Kubernetes, no Terraform required for sandbox

Procedure

Step 1: Sandbox Account Setup

Guide the user through account creation:

# 1. Sign up at https://cloud.gov/sign-up/ with your .gov/.mil email
# 2. Install the CF CLI: https://docs.cloud.gov/platform/getting-started/quickstart-setup/
# 3. Login:
cf login -a api.fr.cloud.gov --sso
# 4. Visit the passcode URL shown, authenticate, paste the code
# 5. Target your sandbox:
cf target -o sandbox-<agency> -s <your-email-prefix>

Note: Sandbox contents are cleared every 90 days. For persistent deployments, the agency needs a cloud.gov organization.

Step 2: Generate manifest.yml

Create a manifest.yml in the project root based on the tech stack from PROJECT_PLAN.md:

Python (FastAPI/Flask/Django):

---
applications:
  - name: <project-name>
    memory: 256M
    instances: 1
    buildpacks:
      - python_buildpack
    command: gunicorn app:app
    env:
      DISABLE_COLLECTSTATIC: 1
    services: []

Node.js/TypeScript:

---
applications:
  - name: <project-name>
    memory: 256M
    instances: 1
    buildpacks:
      - nodejs_buildpack
    command: npm start
    env:
      NODE_ENV: production
    services: []

Go:

---
applications:
  - name: <project-name>
    memory: 128M
    instances: 1
    buildpacks:
      - go_buildpack
    env:
      GOVERSION: go1.22
    services: []

Static site (Astro/Hugo/Jekyll):

---
applications:
  - name: <project-name>
    memory: 64M
    instances: 1
    buildpacks:
      - staticfile_buildpack
    path: dist/

Read the full file on GitHub · 223 lines

Changes

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.

  1. 4d ago First seen · 223 lines · 20 tokens per session scan B 42c67191ba27

Subscribe to this mod's changes

cloudgov-deploy is a skill published in the GitHub repository GSA-TTS/agentic-coding-playbook (23 stars, last pushed 2d ago), licensed CC0-1.0. It adds 20 tokens to every session and 1,497 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens