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/prompts/validate-standards.prompt.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/commands/fadwen/powershell-copilot-standards/validate-standards)<a href="https://agentmods.dev/commands/fadwen/powershell-copilot-standards/validate-standards"><img src="https://agentmods.dev/badge/commands/fadwen/powershell-copilot-standards/validate-standards/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/commands/fadwen/powershell-copilot-standards/validate-standards"><img src="https://agentmods.dev/badge/commands/fadwen/powershell-copilot-standards/validate-standards.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.00008 | $0.00358 |
| Opus 5.5 | $0.00003 | $0.00143 |
| Sonnet 5.5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
validate-standards 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.
What it actually says
Validate this PowerShell code against established community best practices and style guidelines:
Selected Code:
${selection}
Validation Areas:
🏗️ Best Practices Compliance
- Tool Design: Verify functions are reusable with parameter input and pipeline output
- Error Handling: Check for -ErrorAction Stop usage and proper try/catch blocks
- Performance: String concatenation and pipeline efficiency. Flag
+=only where the declared target is below 7.5, in which it remains O(n²) - PowerShell 7.5 optimised it - Security: Validate PSCredential usage and input sanitization
- Modularity: Assess function design and single responsibility principle
🎨 Style Guide Compliance
- Code Layout: One True Brace Style, 4-space indentation, 115-character lines
- Naming: Approved verbs, full command names, PascalCase conventions
- Function Structure: CmdletBinding, proper parameter validation, comment-based help
- Formatting: Operator spacing, parameter alignment, anti-pattern avoidance
📊 Analysis Output
Provide specific feedback on:
- Standards Violations: List specific issues with line numbers
- Style Issues: Formatting and naming problems
- Performance Concerns: Anti-patterns and optimization opportunities
- Security Gaps: Input validation and credential handling issues
- Corrected Code: Show properly formatted version following all standards
Focus on actionable recommendations with before/after code examples that align with PowerShell community standards.
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 First seen · 43 lines · 8 tokens per session scan A 7a395733b720
validate-standards is a command published in the GitHub repository fadwen/Powershell-Copilot-Standards (19 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 358 once invoked, about $0.0000 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-09-16.
Other commands, from other repositories
devkit.typescript.code-review
Provides comprehensive TypeScript monorepo code review for Nx workspaces including NestJS backend, React web, and React Native mobile apps. Use when reviewing architecture, boundaries, security, performance, CI/CD and Nx-specific practices.
review-uv-script
Review uv Python script for PEP 723 compliance and best practices.
package-review
Review the current Python package for best-practice violations — project structure, pyproject.toml, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience.
rust-review
Lightweight Rust code review using clippy.
review
Comprehensive code review for blz changes.
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.