Borrowing it
Nothing to install: this file belongs to adhocteam/cloud-gov-instructions. 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/adhocteam/cloud-gov-instructions/main/.github/copilot-instructions.mdgit 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/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/instructions/adhocteam/cloud-gov-instructions/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/adhocteam/cloud-gov-instructions/copilot-instructions.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.01441 | $0.01441 |
| Opus 5.5 | $0.00576 | $0.00576 |
| Sonnet 5.5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
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 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.
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 — 212 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 and agent-driven workflows)
# Store credentials in a .env file to avoid exposing them in shell history:
# CF_USERNAME=<SERVICE_ACCOUNT_USERNAME>
# CF_PASSWORD=<SERVICE_ACCOUNT_PASSWORD>
# Then source the file and authenticate:
source .env
cf auth
# 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
Security note: Never pass credentials as positional arguments to
cf auth— they will appear in shell history and process listings. Use theCF_USERNAMEandCF_PASSWORDenvironment variables instead. Store them in a.envfile (excluded from version control via.gitignore) and load withsource .env.
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 Changed · +10 lines · +120 tokens per session 436f606a0888
- 1mo 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 1mo ago), licensed MIT. It adds 1,441 tokens to every session, about $0.0058 per session on Opus 5.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
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge bicep.instructions.md
Bicep IaC patterns — file structure, naming, modules, parameters, outputs, linter, security.
plan-forge policy.instructions.md
Azure Policy and Initiative compliance — definitions, assignment, compliance state, exemptions, remediation tasks.
plan-forge terraform.instructions.md
Terraform Azure patterns — file structure, providers, state, naming, security, testing.
plan-forge azd.instructions.md
Azure Developer CLI (azd) patterns — azure.yaml structure, infra folder, tags, hooks, pipelines.