Borrowing it
Nothing to install: this file belongs to GSA-TTS/agentic-coding-playbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GSA-TTS/agentic-coding-playbook/main/.agents/skills/cloudgov-deploy/SKILL.mdgit clone --depth 1 https://github.com/GSA-TTS/agentic-coding-playbookWrote 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/gsa-tts/agentic-coding-playbook/cloudgov-deploy)<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/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/gsa-tts/agentic-coding-playbook/cloudgov-deploy"><img src="https://agentmods.dev/badge/skills/gsa-tts/agentic-coding-playbook/cloudgov-deploy.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.00020 | $0.01497 |
| Opus 5.5 | $0.00008 | $0.00599 |
| Sonnet 5.5 | $0.00004 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00150 |
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 1mo 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/ 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/
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.
- 1mo ago First seen · 223 lines · 20 tokens per session scan B 42c67191ba27
cloudgov-deploy is a skill published in the GitHub repository GSA-TTS/agentic-coding-playbook (37 stars, last pushed yesterday), licensed CC0-1.0. It adds 20 tokens to every session and 1,497 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.