Powershell-Copilot-Standards errorsandlogs.instructions.md

Instructions for adding error handling and structured logs to PowerShell solutions. Structured logs record events in a consistent form, while correlation IDs link messages from one operation.

In plain words
What is it for?
Use it when generating PowerShell functions that need try/catch handling, correlation tracking, verbose progress messages, and tests for failure paths.
Why use it?
It helps diagnose failures and lets a batch continue processing other items when one item fails.

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

Made for: GitHub Copilot.

Per session 2,978 This file is loaded in full into every session.
When invoked 2,978 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.02978 $0.02978
Opus 5 $0.01489 $0.01489
Sonnet 5 $0.00596 $0.00596
Haiku 4.5 $0.00298 $0.00298

Measured 2d ago against content hash 33eb290f0b2d, 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 errorsandlogs.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 2d 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/errorsandlogs.instructions.md · 402 lines

How it starts

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

PowerShell Error Handling and Logging Implementation

Implement robust error handling and structured logging patterns for PowerShell code that ensure proper error management, correlation tracking, and enterprise-grade diagnostic capabilities.

Worked examples: Basic-Function-Example.ps1 and Get-ExampleData.ps1 both generate a correlation ID once in begin, carry it through every message, use $_ in the catch, and continue so one failed item does not abort the batch. Both failure paths are covered by tests.

Error Handling Implementation

Comprehensive Error Handling Pattern

Generate error handling code following this enterprise pattern:

function Verb-Noun {
    [CmdletBinding()]
    param(
        [Parameter(Mandatory = $true)]
        [string]$InputParameter
    )

    # Initialize correlation tracking
    $correlationId = [System.Guid]::NewGuid()
    $ErrorActionPreference = 'Stop'

    try {
        Write-Verbose "Starting operation - CorrelationId: $correlationId"

        # Main operation logic here
        $result = Invoke-Operation -CorrelationId $correlationId

        Write-Verbose "Operation completed successfully - CorrelationId: $correlationId"
        return $result
    }
    catch {
        # Structured error logging
        $errorDetails = @{
            CorrelationId = $correlationId
            Function = $MyInvocation.MyCommand.Name
            ErrorMessage = $_.Exception.Message
            StackTrace = $_.ScriptStackTrace
            Timestamp = Get-Date
            InputParameters = $PSBoundParameters
        }

        Write-Error "Operation failed: $($_.Exception.Message) - CorrelationId: $correlationId"

        # Log to troubleshooting system
        $errorDetails | ConvertTo-Json | Out-File ".\Troubleshooting\Logs\error-$correlationId.json"

        throw
    }
    finally {
        # Resource cleanup
        if ($resource -and $resource -is [System.IDisposable]) {
            $resource.Dispose()
        }
    }
}

Read the full file on GitHub · 402 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. 2d ago First seen · 402 lines · 2,978 tokens per session scan A 33eb290f0b2d

Subscribe to this mod's changes

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