Powershell-Copilot-Standards copilot-instructions.md

Powershell-Copilot-Standards copilot-instructions.md is an instructions file for GitHub Copilot from fadwen/Powershell-Copilot-Standards. It costs 6,635 tokens per session, scanned A, original, MIT.

A set of standards for writing enterprise PowerShell scripts, Microsoft's command-line and automation language. The guidance covers security, input checks, error handling, logging, performance, and common PowerShell practices.

In plain words
What is it for?
Use it when creating reusable PowerShell functions or automation scripts for organizational environments. It also guides pipeline output, modular design, and compliance with community conventions.
Why use it?
It gives generated scripts consistent rules for handling credentials, tracing operations, and recovering from errors. This reduces avoidable security, maintenance, and troubleshooting problems.

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/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/fadwen/Powershell-Copilot-Standards

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for Powershell-Copilot-Standards copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/copilot-instructions.svg)](https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 6,635 This file is loaded in full into every session.
When invoked 6,635 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.06635 $0.06635
Opus 5 $0.03318 $0.03318
Sonnet 5 $0.01327 $0.01327
Haiku 4.5 $0.00664 $0.00664

Measured 3d ago against content hash 69a4ae1b7084, 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 copilot-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/copilot-instructions.md Β· 743 lines

How it starts

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

PowerShell Copilot Instructions

🎯 Core Principles

You are assisting with enterprise PowerShell development that prioritizes security, maintainability, and performance. Always follow these foundational principles:

  1. Security by Design: Implement comprehensive input validation and secure credential handling
  2. Correlation Tracking: Include correlation IDs for audit trails and troubleshooting
  3. Error Resilience: Implement robust error handling with structured logging
  4. Performance Awareness: Write efficient code with appropriate optimization
  5. Community Standards: Follow established PowerShell best practices and style guidelines
  6. Enterprise Integration: Design for scalability and organizational compliance

πŸ“‹ Community Standards Integration

PowerShell Community Standards Compliance

All code generation must comply with established PowerShell community best practices and style guidelines, incorporating expert feedback for accuracy:

Best Practices Enforcement
  • Tool vs Controller Design: Create reusable functions (tools) vs one-time automation scripts (controllers)
  • Modular Architecture: Functions accept input via parameters, output to pipeline for maximum reusability
  • Error Handling Standards: Use proper $_ handling in catch blocks, appropriate null checking patterns
  • Performance Optimization: Context-dependent string operations, test when it matters, use language features over cmdlets
  • Security by Design: Modern credential handling with [PSCredential]::new(), validate all inputs, sanitize data
Style Guide Compliance
  • Code Layout: One True Brace Style (opening brace at end of line), 4-space indentation, 115-character line limit
  • Function Structure: Advanced functions with CmdletBinding, appropriate parameter validation (no redundant attributes)
  • Naming Conventions: Approved PowerShell verbs only (use Get-Verb), full command names, explicit parameter names, PascalCase
  • Documentation Standards: Proper comment-based help format with opening <#, no maintenance-heavy versioning in NOTES

Read the full file on GitHub Β· 743 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 Β· 743 lines Β· 6,635 tokens per session scan A 69a4ae1b7084

Subscribe to this mod's changes

Powershell-Copilot-Standards copilot-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 6,635 tokens to every session, about $0.0332 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.

Related

Other instructions, from other repositories