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 commands/srnichols/plan-forge/new-pipelineWrote 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/commands/srnichols/plan-forge/new-pipeline)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-pipeline"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-pipeline.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.00019 | $0.01664 |
| Opus 5 | $0.00010 | $0.00832 |
| Sonnet 5 | $0.00004 | $0.00333 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
new-pipeline 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 today.
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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Infrastructure Pipeline
Scaffold a CI/CD pipeline for Azure IaC deployments with validate → what-if → deploy → verify stages.
Required Information
Before generating, ask for:
- Pipeline provider — GitHub Actions or Azure DevOps?
- IaC tool — Bicep, Terraform, or azd?
- Environments — which environments exist? (dev, staging, prod)
- Trigger — push to main? PR? Manual dispatch?
GitHub Actions — Bicep
# .github/workflows/infra-deploy.yml
name: Infrastructure Deploy
on:
push:
branches: [main]
paths: ['infra/**']
pull_request:
branches: [main]
paths: ['infra/**']
workflow_dispatch:
inputs:
environment:
description: 'Target environment'
required: true
default: 'dev'
type: choice
options: [dev, staging, prod]
permissions:
id-token: write
contents: read
jobs:
validate:
name: Validate
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: azure/login@v2
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- run: az bicep install
- run: az bicep lint --file infra/main.bicep
- 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.event_name != 'pull_request'
steps:
- uses: actions/checkout@v4
- uses: azure/login@v2
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- 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: Invoke-Pester -Path ./tests/integration -Output Detailed
deploy-prod:
name: Deploy Production
needs: deploy-dev
runs-on: ubuntu-latest
environment: prod # requires manual approval gate in GitHub environments
steps:
- uses: actions/checkout@v4
- uses: azure/login@v2
with:
client-id: ${{ secrets.AZURE_CLIENT_ID }}
tenant-id: ${{ secrets.AZURE_TENANT_ID }}
subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
- uses: azure/arm-deploy@v2
with:
resourceGroupName: ${{ vars.PROD_RESOURCE_GROUP }}
template: infra/main.bicep
parameters: infra/main.parameters.json environmentName=prod
failOnStdErr: true
- name: Smoke Test
shell: pwsh
run: Invoke-Pester -Path ./tests/integration -Output Detailed
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.
- today First seen · 224 lines · 19 tokens per session scan A 337ae87f2e35
new-pipeline is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,664 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
arrange-workspace-flow-technical-context
Phase 4 Technical context of arrange-workspace-flow.
deploy-setup
Wire CI + secrets for a fresh storefront. Run once after /init-store before the first push to main.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.