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.
npx agentmods add instructions/fadwen/powershell-copilot-standards/style-enforcementgit 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/style-enforcement)<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/style-enforcement"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/style-enforcement.svg" alt="Measured on agentmods" 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 | $0.00652 | $0.00652 |
| Opus 5 | $0.00326 | $0.00326 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
Powershell-Copilot-Standards style-enforcement.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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Style Guide Enforcement
Automatically enforce PowerShell community style guidelines in all code generation.
Worked example: every file under Documentation/Examples is written to these rules and passes the repository's own quality gates. When the wording here is ambiguous, match the examples.
Mandatory Style Patterns
Code Formatting
- Brace Style: One True Brace Style (opening brace at end of line)
- Indentation: 4 spaces, never tabs
- Line Length: Maximum 115 characters
- Blank Lines: 2 blank lines before functions, 1 between methods
A team that wants these checked mechanically does not need a settings file - PSScriptAnalyzer ships
CodeFormattingOTBS, which already configures the brace style, 4-space indentation, whitespace and
assignment alignment above:
Invoke-ScriptAnalyzer -Path . -Recurse -Settings CodeFormattingOTBS
The 115-character limit is the one rule it does not include; add PSAvoidLongLines if the team
wants it enforced. Adopting either is their choice - these standards describe the practices, not the
audit configuration.
Parameter Formatting
# Correct parameter block formatting
param(
[Parameter(Mandatory = $true,
ValueFromPipeline = $true,
ValueFromPipelineByPropertyName = $true)]
[ValidateNotNullOrEmpty()]
[string[]]$ComputerName,
[Parameter()]
[System.Management.Automation.PSCredential]
[System.Management.Automation.Credential()]
$Credential = [System.Management.Automation.PSCredential]::Empty
)
Operator Spacing
# Correct spacing around operators
$result = $value1 + $value2
$condition = ($status -eq 'Running') -and ($service -ne $null)
# Correct parameter spacing
Get-Process -Name "powershell" -ComputerName $servers
Anti-Patterns to Avoid
# Avoid backticks for line continuation
# Instead of:
Get-WmiObject -Class Win32_LogicalDisk `
-Filter "DriveType=3" `
-ComputerName $server
# Use splatting:
$params = @{
Class = 'Win32_LogicalDisk'
Filter = 'DriveType=3'
ComputerName = $server
}
Get-WmiObject @params
# Avoid Write-Host unless specifically needed for colored output
# Use Write-Output, Write-Verbose, Write-Information instead
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.
- 4d ago First seen · 96 lines · 652 tokens per session scan A af2406dac1a5
Powershell-Copilot-Standards style-enforcement.instructions.md is an instructions file published in the GitHub repository fadwen/Powershell-Copilot-Standards (18 stars, last pushed 4d ago), licensed MIT. It adds 652 tokens to every session, about $0.0033 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.
Other instructions, from other repositories
oh-my-posh AGENTS.md
AGENTS.md instructions for JanDeDobbeleer/oh-my-posh, covering agent instructions, project overview, tech stack, key commands and go - run from src/.
oh-my-posh copilot-instructions.md
Copilot 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.
oh-my-posh markdown.instructions.md
Instructions for JanDeDobbeleer/oh-my-posh: Refer to skills/markdown/SKILL.md for the full Markdown formatting standards.
oh-my-posh powershell.instructions.md
Instructions for JanDeDobbeleer/oh-my-posh: Refer to skills/powershell/SKILL.md for the full PowerShell coding standards.
oh-my-posh golang.instructions.md
Instructions for JanDeDobbeleer/oh-my-posh: Refer to skills/golang/SKILL.md for the full Go coding standards.
psmux AGENTS.md
AGENTS.md instructions for psmux/psmux, covering agent instructions and test isolation.