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/analyzegit clone --depth 1 https://github.com/fadwen/Powershell-Copilot-StandardsWhat 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.00752 | $0.00752 |
| Opus 5 | $0.00376 | $0.00376 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
Powershell-Copilot-Standards analyze.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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Code Analysis
Analyze the provided PowerShell code using enterprise-grade analysis standards. Perform a comprehensive review covering code quality, security, performance, and compliance with organizational standards.
Analysis Framework
Execute the following analysis components:
1. Code Quality Assessment
- PSScriptAnalyzer Validation: Check against all standard rules plus enterprise-specific rules
- Best Practices Compliance: Verify adherence to PowerShell development standards
- Code Structure: Evaluate function design, parameter validation, and pipeline efficiency
- Documentation Quality: Assess comment-based help completeness and accuracy
2. Security Analysis
- Credential Leak Detection: Scan for hardcoded passwords, API keys, or sensitive data
- Input Validation: Verify all user inputs are properly validated and sanitized
- Path Traversal Protection: Check for unsafe file path handling
- Injection Prevention: Identify potential code injection vulnerabilities
3. Performance Evaluation
- Memory Usage: Assess memory management and resource disposal
- Pipeline Optimization: Evaluate pipeline usage and efficiency
- Scalability: Review code for performance with large datasets
- Algorithm Efficiency: Identify optimization opportunities
4. Compliance Verification
- PowerShell Standards: Verify compliance with approved verbs and naming conventions
- File Organization: Check adherence to standardized folder structure
- Testing Coverage: Evaluate test completeness and quality
- Error Handling: Assess error handling patterns and correlation tracking
Required Output Format
Provide analysis results in this structured format:
🚨 Critical Issues (Must Fix)
- List any critical security vulnerabilities or breaking errors
- Include specific line numbers and remediation steps
⚠️ High Priority Issues
- Security concerns that should be addressed before production
- Performance bottlenecks affecting scalability
- Standards violations impacting maintainability
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 · 107 lines · 752 tokens per session scan A aa0ff334e0c2
Powershell-Copilot-Standards analyze.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 752 tokens to every session, about $0.0038 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
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
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.