Use it when generating self-contained PowerShell tests with assertions, coverage goals, and checks for code behavior and quality.

It gives tests a consistent structure and quality checks, including unit, integration, performance, and security testing.

Powershell-Copilot-Standards pester.instructions.md

Q: What is Powershell-Copilot-Standards pester.instructions.md?

Instructions for creating Pester 6 test suites for PowerShell code. Pester is PowerShell's testing framework, used to check that code behaves as expected.

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/pester

Clone the repo

git clone --depth 1 https://github.com/fadwen/Powershell-Copilot-Standards

Made for: GitHub Copilot.

Per session 2,416 This file is loaded in full into every session.

When invoked 2,416 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.

Model	Per session	Once invoked
Fable 5	$0.02416	$0.02416
Opus 5	$0.01208	$0.01208
Sonnet 5	$0.00483	$0.00483
Haiku 4.5	$0.00242	$0.00242

Measured 2d ago against content hash 6b7181b82503, 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 pester.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/pester.instructions.md · 216 lines

How it starts

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

PowerShell Pester Testing - Core Instructions

Generate enterprise-grade Pester test suites following these core requirements.

Target version: Pester 6.1+ on Windows PowerShell 5.1 or PowerShell 7.4+. Pester 6 removed support for PowerShell 3, 4, 6, and unsupported 7.x. 6.1 is additive over 6.0 - no test file needs to change to move between them.

NOTE: Do not use Unicode emojis in any generated code, documentation, or test output. Use plain text descriptions and standard ASCII characters only.

Quick Reference

Test Structure Requirements

Directory Structure: Follow Test Structure Guide
Coverage Target: Minimum 80% code coverage for production code
Test Types: Unit (mandatory), Integration, Performance, Security
Quality Gates: All tests pass, performance within limits, security validation
File Isolation: Every test file must be self-contained - see below

Core Test Patterns

Generate tests using these templates:

Unit Tests: Use Unit Test Template
Integration Tests: Use Integration Test Template
Performance Tests: Use Performance Test Template
Security Tests: Use Security Test Template

Assertions

Guide: Use Assertion Guide
New test files: prefer the Pester 6 Should-* assertions (dash, no space) - they are type-aware and produce far better failure messages.
Existing files: keep the file's existing style. Do not mix Should -Be and Should-Be within a single file.
Do not set Should.DisableV5 = $true until every test file in the repository is migrated.
Custom assertions: the Should-* set is open for extension in 6.1 via New-ShouldAssertion - see Custom Assertion Guide. Write one only when the same domain rule is asserted across several files and naming the offending value is the point.

Read the full file on GitHub · 216 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.

2d ago First seen · 216 lines · 2,416 tokens per session scan A 6b7181b82503

Subscribe to this mod's changes

Powershell-Copilot-Standards pester.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,416 tokens to every session, about $0.0121 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.

Testing githubcopilot powershell

oh-my-posh AGENTS.md

Instructions for JanDeDobbeleer/oh-my-posh, covering agent instructions, project overview, tech stack, key commands and go - run from src/.

JanDeDobbeleer/oh-my-posh · 1,987 tokens

oh-my-posh copilot-instructions.md

Instructions for JanDeDobbeleer/oh-my-posh: All agent guidance for this repository lives in AGENTS.md: project overview, key commands, architecture orientation, coding and commit conventions, skills, and the project-knowledge workflow. Follow it in full.

JanDeDobbeleer/oh-my-posh · 54 tokens