Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/srnichols/plan-forgenpx agentmods add instructions/srnichols/plan-forge/deployWrote 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/srnichols/plan-forge/deploy)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/deploy"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/deploy/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/srnichols/plan-forge/deploy"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/deploy.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.01667 | $0.01667 |
| Opus 5.5 | $0.00667 | $0.00667 |
| Sonnet 5.5 | $0.00333 | $0.00333 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
plan-forge deploy.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 19d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure IaC Pipeline Patterns
Authentication — Workload Identity Federation (OIDC)
Use OIDC/Workload Identity Federation everywhere — no stored client secrets.
GitHub Actions Setup
# One-time setup: configure the federated credential
azd pipeline config # automatically configures OIDC for GitHub Actions
Required secrets in GitHub:
AZURE_CLIENT_ID— App Registration client IDAZURE_TENANT_ID— Azure AD tenant IDAZURE_SUBSCRIPTION_ID— target subscription
Azure DevOps Setup
Use a service connection with Workload Identity Federation:
Project Settings → Service connections → New → Azure Resource Manager → Workload Identity Federation
GitHub Actions — Bicep Deployment Pipeline
# .github/workflows/infra-deploy.yml
name: Infrastructure Deploy
on:
push:
branches: [main]
paths: ['infra/**']
pull_request:
branches: [main]
paths: ['infra/**']
workflow_dispatch:
permissions:
id-token: write # required for OIDC
contents: read
jobs:
validate:
name: Validate
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v7
- name: Azure Login (OIDC)
uses: azure/login@v3
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- name: Install Bicep CLI
run: az bicep install
- name: Lint Bicep
run: az bicep lint --file infra/main.bicep
- name: Bicep Build (validate ARM output)
run: az bicep build --file infra/main.bicep
- name: What-If Analysis
run: |
az deployment group what-if \
--resource-group ${{ vars.RESOURCE_GROUP }} \
--template-file infra/main.bicep \
--parameters infra/main.parameters.json \
--no-pretty-print
deploy-dev:
name: Deploy Dev
needs: validate
runs-on: ubuntu-latest
environment: dev
if: github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v7
- uses: azure/login@v3
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- name: Deploy Bicep
uses: azure/arm-deploy@v2
with:
resourceGroupName: ${{ vars.DEV_RESOURCE_GROUP }}
template: infra/main.bicep
parameters: infra/main.parameters.json environmentName=dev
failOnStdErr: true
- name: Smoke Test
shell: pwsh
run: ./scripts/Invoke-SmokeTest.ps1 -EnvironmentName dev
deploy-prod:
name: Deploy Production
needs: deploy-dev
runs-on: ubuntu-latest
environment: prod # requires manual approval gate in GitHub
steps:
- uses: actions/checkout@v7
- uses: azure/login@v3
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- name: Deploy Bicep
uses: azure/arm-deploy@v2
with:
resourceGroupName: ${{ vars.PROD_RESOURCE_GROUP }}
template: infra/main.bicep
parameters: infra/main.parameters.json environmentName=prod
failOnStdErr: true
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.
- 19d ago Changed 9f9a03e086bb
- 1mo ago First seen · 238 lines · 1,667 tokens per session scan A 47f7a53e35a2
plan-forge deploy.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 7d ago), licensed MIT. It adds 1,667 tokens to every session, about $0.0067 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.