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/manifest.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/manifest)<a href="https://agentmods.dev/instructions/adhocteam/cloud-gov-instructions/manifest"><img src="https://agentmods.dev/badge/instructions/adhocteam/cloud-gov-instructions/manifest.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.1 | $0.02029 | $0.02029 |
| Opus 5 | $0.01014 | $0.01014 |
| Sonnet 5 | $0.00406 | $0.00406 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
cloud-gov-instructions manifest.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 6d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud.gov Manifest Configuration Instructions
This document provides guidance for creating and configuring manifest.yml files for cloud.gov deployments.
Overview
The manifest.yml file defines your application's deployment configuration. It specifies memory, instances, services, environment variables, and other settings.
Basic Manifest Structure
---
applications:
- name: my-application
memory: 512M
disk_quota: 1G
instances: 2
buildpacks:
- python_buildpack
command: gunicorn app:app
env:
ENVIRONMENT: production
services:
- my-database
- my-s3-bucket
routes:
- route: my-app.app.cloud.gov
Manifest Properties Reference
Required Properties
| Property | Description | Example |
|---|---|---|
name |
Application name (must be unique in space) | my-app |
Resource Allocation
| Property | Description | Default | Example |
|---|---|---|---|
memory |
Memory allocation per instance | 1G |
512M, 1G, 2G |
disk_quota |
Disk space per instance | 1G |
512M, 2G |
instances |
Number of application instances | 1 |
2, 3 |
Best Practices:
- Always specify
memoryexplicitly - Use
instances: 2or more for production - Size memory based on actual application needs
Buildpack Configuration
applications:
- name: my-app
buildpacks:
- python_buildpack
Available buildpacks:
python_buildpacknodejs_buildpackruby_buildpackjava_buildpackgo_buildpackphp_buildpackdotnet_core_buildpackstaticfile_buildpackbinary_buildpack
Multiple Buildpacks
applications:
- name: my-app
buildpacks:
- nodejs_buildpack # Runs first
- python_buildpack # Runs second
Command and Process Configuration
applications:
- name: my-app
command: gunicorn app:app --bind 0.0.0.0:$PORT --workers 3
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.
- 6d ago First seen · 400 lines · 2,029 tokens per session scan A 76ce211ae9db
cloud-gov-instructions manifest.instructions.md is an instructions file published in the GitHub repository adhocteam/cloud-gov-instructions (10 stars, last pushed 6mo ago), licensed MIT. It adds 2,029 tokens to every session, about $0.0101 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
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 waf.instructions.md
Azure Well-Architected Framework (WAF) guardrails — Reliability, Security, Cost, Operational Excellence, Performance.