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/instructions/services.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/services)<a href="https://agentmods.dev/instructions/adhocteam/cloud-gov-instructions/services"><img src="https://agentmods.dev/badge/instructions/adhocteam/cloud-gov-instructions/services/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/services"><img src="https://agentmods.dev/badge/instructions/adhocteam/cloud-gov-instructions/services.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.02641 | $0.02641 |
| Opus 5.5 | $0.01056 | $0.01056 |
| Sonnet 5.5 | $0.00528 | $0.00528 |
| Haiku 4.5 | $0.00264 | $0.00264 |
Grade A, and why
cloud-gov-instructions services.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 — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud.gov Services Instructions
This document provides guidance for provisioning and using cloud.gov managed services including databases, S3 storage, Redis, and more.
Overview
Cloud.gov provides managed services through a marketplace. Services are:
- Created with
cf create-service - Bound to applications to provide credentials
- Accessed via the
VCAP_SERVICESenvironment variable
Listing Available Services
# View all available services
cf marketplace
# View plans for a specific service
cf marketplace -s aws-rds
cf marketplace -s s3
Service Lifecycle
Create a Service Instance
cf create-service <SERVICE> <PLAN> <INSTANCE_NAME>
Bind to an Application
cf bind-service <APP_NAME> <INSTANCE_NAME>
cf restage <APP_NAME>
Or Bind via manifest.yml
applications:
- name: my-app
services:
- my-database
- my-s3-bucket
Unbind and Delete
cf unbind-service <APP_NAME> <INSTANCE_NAME>
cf delete-service <INSTANCE_NAME>
Relational Databases (AWS RDS)
Available Plans
| Plan | Description |
|---|---|
micro-psql |
Single-AZ PostgreSQL, 1 core, 1 GiB memory |
small-psql |
Single-AZ PostgreSQL, 1 core, 2 GiB memory |
medium-psql |
Single-AZ PostgreSQL, 1 core, 4 GiB memory |
*-psql-redundant |
Multi-AZ PostgreSQL (production recommended) |
small-mysql |
Single-AZ MySQL, 1 core, 2 GiB memory |
*-mysql-redundant |
Multi-AZ MySQL (production recommended) |
Sandbox spaces: Only micro-psql and small-mysql available.
Create PostgreSQL Database
# Development
cf create-service aws-rds micro-psql my-database
# Production (Multi-AZ)
cf create-service aws-rds small-psql-redundant my-database
# With custom storage size
cf create-service aws-rds small-psql my-database -c '{"storage": 50}'
# With specific version
cf create-service aws-rds micro-psql my-database -c '{"version": "15"}'
Create MySQL Database
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 · 456 lines · 2,641 tokens per session scan A 2b48f4cb025f
cloud-gov-instructions services.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 2,641 tokens to every session, about $0.0106 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.