Powershell-Copilot-Standards community-standards.instructions.md

Powershell-Copilot-Standards community-standards.instructions.md is an instructions file for GitHub Copilot from fadwen/Powershell-Copilot-Standards. It costs 1,361 tokens per session, scanned A, original, MIT.

A set of instructions for writing and reviewing PowerShell code according to established community practices, such as reusable commands, pipeline support, raw data output, and structured error handling.

In plain words
What is it for?
Use it when creating PowerShell functions, scripts, automation tools, or code reviews where standard design and error-handling practices matter.
Why use it?
It helps keep PowerShell code consistent, reusable, and easier to combine with other commands or automation.

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/community-standards
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 community-standards.instructions.md

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

Measured 5d ago against content hash 927a22dd8070, 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 community-standards.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 5d 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/community-standards.instructions.md · 221 lines

How it starts

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

PowerShell Community Standards Integration

Integrate established PowerShell community best practices and style guidelines into all code generation and analysis.

Best Practices Implementation

Tool Design Patterns

# Tools (reusable functions) - accept input via parameters, output to pipeline
function Get-ServerInfo {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory = $true, ValueFromPipeline = $true)]
        [string[]]$ComputerName
    )

    process {
        foreach ($computer in $ComputerName) {
            # Return raw data for maximum reusability
            [PSCustomObject]@{
                ComputerName = $computer
                Status = Test-Connection $computer -Count 1 -Quiet
                LastBootTime = (Get-CimInstance Win32_OperatingSystem -ComputerName $computer).LastBootUpTime
                # Raw data, no formatting
            }
        }
    }
}

# Controllers (automation scripts) - can format data for specific purpose
$servers = Get-Content servers.txt
$results = $servers | Get-ServerInfo | Where-Object Status -eq $true
$results | Format-Table -AutoSize  # Controller can format for display

Error Handling Patterns

# Use -ErrorAction Stop for trappable exceptions
try {
    $result = Get-Something -Parameter $value -ErrorAction Stop

    # Put entire transaction in try block, not just the risky part
    Process-Result $result
    Update-Database $result
    Send-Notification "Success"

} catch {
    # Copy error immediately to avoid $Error[0] changes
    $currentError = $Error[0]

    Write-Error "Operation failed: $($currentError.Exception.Message)"
    # Include correlation ID for traceability
    throw
}

Performance Patterns

# Prefer language features over cmdlets for performance
# Instead of: Get-Service | Where-Object Status -eq 'Running'
# Use: Get-Service | Where Status -eq Running

# Use StringBuilder for string concatenation
$sb = [System.Text.StringBuilder]::new()
foreach ($item in $collection) {
    [void]$sb.AppendLine("Processing: $item")
}
$result = $sb.ToString()

# Avoid appending to arrays in loops
$results = foreach ($item in $collection) {
    Process-Item $item  # Output to pipeline instead
}

Read the full file on GitHub · 221 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. 5d ago First seen · 221 lines · 1,361 tokens per session scan A 927a22dd8070

Subscribe to this mod's changes

Powershell-Copilot-Standards community-standards.instructions.md is an instructions file published in the GitHub repository fadwen/Powershell-Copilot-Standards (18 stars, last pushed 5d ago), licensed MIT. It adds 1,361 tokens to every session, about $0.0068 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.