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/comments.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/comments)<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/comments"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/comments/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/comments"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/comments.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.02429 | $0.02429 |
| Opus 5.5 | $0.00972 | $0.00972 |
| Sonnet 5.5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
Powershell-Copilot-Standards comments.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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Help Content Standards
Generate comprehensive, enterprise-grade help for PowerShell functions that serves as both technical
documentation and business communication. Create help that supports automatic README generation and provides full
Get-Help functionality.
Where Help Lives
This file defines what good help content contains. Where that content is written depends on whether the function is exported:
| Function | Help lives in | Notes |
|---|---|---|
Exported (Public/) in a module |
PlatyPS Markdown under docs/ModuleName/ |
The .ps1 keeps only # .EXTERNALHELP plus a one-line .SYNOPSIS |
Private (Private/) in a module |
Full comment-based help in the .ps1 |
PlatyPS never sees these - the comment block is the only documentation |
| Standalone script or function | Full comment-based help in the .ps1 |
No module, no MAML, no PlatyPS |
Every standard below — description structure, per-parameter content, three progressive examples, enterprise notes — applies in all three cases. Only the file it is typed into changes.
For the generation, update, and build mechanics, see
platyps.instructions.md. Do not add detail to a public function's
comment block: .EXTERNALHELP makes Get-Help ignore it, so the effort is invisible to users and
becomes a second copy that drifts.
Help Generation Requirements
Worked example: Basic-Function-Example.ps1 carries a complete help block in the form described here - synopsis, description, per-parameter text, multiple examples with expected output, and
.NOTESwith troubleshooting links but no change history. It is a standalone function, so the whole block lives in the.ps1. In a module, that same content is what belongs in the command's Markdown file.
Mandatory Sections
Generate complete comment-based help including all required sections:
.SYNOPSIS
- Use approved PowerShell verbs (Get, Set, New, Remove, etc.)
- Maximum 80 characters
- Focus on primary action and business value
- Avoid technical jargon unless necessary
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 · 305 lines · 2,429 tokens per session scan A df96fa63492b
Powershell-Copilot-Standards comments.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,429 tokens to every session, about $0.0097 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.