Powershell-Copilot-Standards cicd.instructions.md

Instructions for creating continuous integration and delivery (CI/CD) pipelines for PowerShell projects. CI/CD automatically checks code and can deploy it to target environments.

In plain words
What is it for?
It is for setting up pipelines in services such as GitHub Actions or Azure DevOps, testing PowerShell across versions, checking code quality, scanning credentials, and deploying packages or scripts.
Why use it?
It provides a defined process for testing, quality checks, security scans, and deployment instead of relying on manual steps.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/fadwen/powershell-copilot-standards/cicd
Clone the repo
git clone --depth 1 https://github.com/fadwen/Powershell-Copilot-Standards

Made for: GitHub Copilot.

Per session 2,504 This file is loaded in full into every session.
When invoked 2,504 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02504 $0.02504
Opus 5 $0.01252 $0.01252
Sonnet 5 $0.00501 $0.00501
Haiku 4.5 $0.00250 $0.00250

Measured 3d ago against content hash 5d8911c31315, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Powershell-Copilot-Standards cicd.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 3d 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.

.github/instructions/cicd.instructions.md · 368 lines

How it starts

The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PowerShell CI/CD Pipeline Configuration

Create robust CI/CD pipelines for PowerShell projects with automated testing, quality gates, security scanning, and deployment automation. Support multiple platforms while maintaining enterprise standards.

Pipeline Requirements Assessment

First, determine the pipeline requirements:

Project Information Needed

  • Platform Preference: Azure DevOps, GitHub Actions, GitLab CI, or Jenkins
  • PowerShell Versions: PowerShell 7.6 (LTS, default), or 5.1 + 7.6 when Windows PowerShell support is required. Retire 7.4/7.5-only matrices before 10-Nov-2026, when both reach end of support
  • Target Environments: Development, Testing, Staging, Production
  • Deployment Targets: PowerShell Gallery, internal repositories, or direct deployment
  • Security Requirements: Code signing, credential management, compliance scanning

Quality Gates to Implement

  • Code Quality: PSScriptAnalyzer validation with zero errors
  • Testing: Minimum 80% code coverage with Pester tests
  • Security: Credential scanning and vulnerability assessment
  • Performance: Execution time and memory usage baselines
  • Documentation: README and troubleshooting documentation validation
  • Help Docs: PlatyPS Markdown structure valid, no placeholders, no drift against exported commands

Pipeline Configuration

Azure DevOps Pipeline

Generate complete Azure DevOps YAML pipeline with:

# Key components to include:
stages:
  - Build and Validate
  - Security Scanning
  - Package Creation
  - Environment Deployments
  - PowerShell Gallery Publishing

Required Pipeline Features:

  • Multi-stage pipeline with approval gates
  • Parallel job execution for different PowerShell versions
  • Artifact management and retention
  • Environment-specific variable groups
  • Integration with Azure Key Vault for secrets
  • Automated rollback on deployment failure

GitHub Actions Workflow

Create comprehensive GitHub Actions workflow including:

Read the full file on GitHub · 368 lines

Changes

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.

  1. 3d ago First seen · 368 lines · 2,504 tokens per session scan A 5d8911c31315

Subscribe to this mod's changes

Powershell-Copilot-Standards cicd.instructions.md is an instructions file published in the GitHub repository fadwen/Powershell-Copilot-Standards (19 stars, last pushed 3d ago), licensed MIT. It adds 2,504 tokens to every session, about $0.0125 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-30.