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 instructions/adhocteam/cloud-gov-instructions/deploymentgit clone --depth 1 https://github.com/adhocteam/cloud-gov-instructionsWrote 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/instructions/adhocteam/cloud-gov-instructions/deployment)<a href="https://agentmods.dev/instructions/adhocteam/cloud-gov-instructions/deployment"><img src="https://agentmods.dev/badge/instructions/adhocteam/cloud-gov-instructions/deployment.svg" alt="Measured on agentmods" 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 | $0.01614 | $0.01614 |
| Opus 5 | $0.00807 | $0.00807 |
| Sonnet 5 | $0.00323 | $0.00323 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
cloud-gov-instructions deployment.instructions.md scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://<APP_NAME>.app.cloud.gov/health How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud.gov Deployment Instructions
This document provides guidance for deploying applications to cloud.gov using the Cloud Foundry CLI.
Overview
Cloud.gov uses cf push as the primary deployment command. The platform builds your application using buildpacks and runs it in isolated containers.
Prerequisites
- Cloud Foundry CLI installed (
cfcommand available) - Authenticated to cloud.gov:
cf login -a api.fr.cloud.gov --sso - Targeted the correct org and space:
cf target -o <ORG> -s <SPACE>
Basic Deployment Workflow
1. Prepare Your Application
Ensure your application follows these principles:
- Stateless: Don't write to local filesystem for persistent data
- 12-Factor: Follow Twelve-Factor App methodology
- Quick startup: Applications should start within 60 seconds
- Health endpoint: Implement
/healthor similar for monitoring
2. Create Required Files
manifest.yml
---
applications:
- name: my-application
memory: 512M
instances: 2
buildpacks:
- python_buildpack
env:
ENVIRONMENT: production
services:
- my-database
routes:
- route: my-app.app.cloud.gov
.cfignore
Exclude unnecessary files from deployment:
.git/
.gitignore
node_modules/
__pycache__/
*.pyc
.env
.env.*
tests/
docs/
*.md
!README.md
.vscode/
.idea/
.profile (optional)
Shell script run before app starts:
#!/bin/bash
# Set runtime environment variables
export APP_STARTED_AT=$(date)
Procfile (optional)
Define process types:
web: gunicorn app:app --bind 0.0.0.0:$PORT
worker: python worker.py
3. Deploy the Application
# Basic deployment
cf push
# Deploy with specific manifest
cf push -f manifest.yml
# Deploy without starting (useful for binding services first)
cf push --no-start
# Deploy with a specific app name (overrides manifest)
cf push my-app-name
4. Verify Deployment
# Check application status
cf app <APP_NAME>
# View recent logs
cf logs <APP_NAME> --recent
# Stream live logs
cf logs <APP_NAME>
# Check application health
curl https://<APP_NAME>.app.cloud.gov/health
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.
- 3d ago First seen · 318 lines · 1,614 tokens per session scan A cf88017489c2
cloud-gov-instructions deployment.instructions.md is an instructions file published in the GitHub repository adhocteam/cloud-gov-instructions (10 stars, last pushed 5mo ago), licensed MIT. It adds 1,614 tokens to every session, about $0.0081 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
azure-search-openai-demo bicep.instructions.md
Infrastructure as Code with Bicep.
obsidian-copilot AGENTS.md
AGENTS.md instructions for logancyang/obsidian-copilot, covering agents.md, commands, core principles (apply to every change), task-specific guides and important notes.
optio CLAUDE.md
Instructions for jonwiggins/optio, covering claude.md, what is optio?, architecture, pod-per-repo with worktrees and worktree lifecycle.
obsidian-copilot CLAUDE.md
Claude Code instructions for logancyang/obsidian-copilot, a project described as: THE Copilot in Obsidian.
apex-accelerator copilot-instructions.md
Instructions for jonathan-vella/apex-accelerator, covering apex - copilot instructions, azure defaults (canonical), default regions, required tags (azure policy enforced) and security baseline + avm mandate.
apex-accelerator iac-terraform-best-practices.instructions.md
Terraform-specific IaC best practices for Azure templates. AVM-first, CAF naming, security baseline, provider pins.