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/analyze.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/analyze)<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/analyze"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/analyze/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/analyze"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/analyze.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.00752 | $0.00752 |
| Opus 5.5 | $0.00301 | $0.00301 |
| Sonnet 5.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 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 — 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.
- 1mo 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 1mo ago), licensed MIT. It adds 752 tokens to every session, about $0.0030 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.