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/copilot-instructionsgit 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/copilot-instructions)<a href="https://agentmods.dev/instructions/adhocteam/cloud-gov-instructions/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/adhocteam/cloud-gov-instructions/copilot-instructions.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.01321 | $0.01321 |
| Opus 5 | $0.00660 | $0.00660 |
| Sonnet 5 | $0.00264 | $0.00264 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
cloud-gov-instructions copilot-instructions.md 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 5d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud.gov Development Instructions
This repository contains an application deployed to cloud.gov, a FedRAMP-authorized Platform as a Service (PaaS) operated by the U.S. General Services Administration (GSA). These instructions help AI coding assistants understand cloud.gov conventions and best practices.
Platform Overview
Cloud.gov is built on Cloud Foundry and provides:
- FedRAMP Moderate authorization - Inherit ~60% of NIST SP 800-53 controls
- Self-service deployment - Deploy with
cf push, no infrastructure tickets required - Managed services - Databases, object storage, and more via the marketplace
- Isolated environments - Separate spaces for dev, staging, and production
Key Concepts
Organizations and Spaces
- Organization (org): Top-level container for users, spaces, and quotas
- Space: Isolated environment within an org (e.g.,
dev,staging,prod) - Target: Set your working org/space with
cf target -o <ORG> -s <SPACE>
Applications
- Applications are deployed as containers built from source code using buildpacks
- Each app instance runs in an isolated container with its own memory and disk allocation
- Apps should follow Twelve-Factor App principles
Common CF CLI Commands
Authentication
# Target the cloud.gov API endpoint
cf api api.fr.cloud.gov
# Login with service account credentials (for CI/CD)
cf auth <USERNAME> <PASSWORD>
# Target an org and space
cf target -o <ORG> -s <SPACE>
# Login with SSO (recommended for interactive use)
cf login -a api.fr.cloud.gov --sso
Deployment
# Deploy an application
cf push <APP_NAME>
# Deploy with a specific manifest file
cf push -f manifest.yml
# Deploy without starting the app
cf push <APP_NAME> --no-start
# View application status
cf app <APP_NAME>
# View recent logs
cf logs <APP_NAME> --recent
# Stream live logs
cf logs <APP_NAME>
Application Management
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.
- 5d ago First seen · 202 lines · 1,321 tokens per session scan A 0867fb3c661a
cloud-gov-instructions copilot-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,321 tokens to every session, about $0.0066 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 instructions, from other repositories
azure-search-openai-demo bicep.instructions.md
Infrastructure as Code with Bicep.
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 iac-terraform-best-practices.instructions.md
Terraform-specific IaC best practices for Azure templates. AVM-first, CAF naming, security baseline, provider pins.
apex-accelerator iac-bicep-best-practices.instructions.md
Bicep-specific IaC best practices for Azure templates. Security baseline, naming, AVM mandate, anti-patterns.
apex-accelerator governance-discovery.instructions.md
MANDATORY Azure Policy discovery requirements for governance constraints.