Borrowing it
Nothing to install: this file belongs to fadwen/Powershell-Copilot-Standards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fadwen/Powershell-Copilot-Standards/main/.github/instructions/pester.instructions.mdgit clone --depth 1 https://github.com/fadwen/Powershell-Copilot-StandardsWrote 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.
[](https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/pester)<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/pester"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/pester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/pester"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/pester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.02757 | $0.02757 |
| Opus 5.5 | $0.01103 | $0.01103 |
| Sonnet 5.5 | $0.00551 | $0.00551 |
| Haiku 4.5 | $0.00276 | $0.00276 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 235 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.2+ on Windows PowerShell 5.1 or PowerShell 7.4+. Pester 6 removed
support for PowerShell 3, 4, 6, and unsupported 7.x. 6.1 and 6.2 are additive for test files - no
test file needs to change to move between 6.0, 6.1, and 6.2. The one thing 6.2 changes underneath a
suite is Pester.BeforeContainer.ps1: top-level code in it now runs at discovery only, so run-time
setup there must sit in a BeforeAll - see
Moving From 6.1 to 6.2.
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 -BeandShould-Bewithin a single file. - Do not set
Should.DisableV5 = $trueuntil every test file in the repository is migrated. - Custom assertions: the
Should-*set is open for extension in 6.1 viaNew-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.
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.
- 1mo ago Changed · +19 lines · +341 tokens per session 9174704fa697
- 1mo ago First seen · 216 lines · 2,416 tokens per session scan A 6b7181b82503
Powershell-Copilot-Standards pester.instructions.md is an instructions file published in the GitHub repository fadwen/Powershell-Copilot-Standards (19 stars, last pushed 1mo ago), licensed MIT. It adds 2,757 tokens to every session, about $0.0110 per session on Opus 5.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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.