Use it when designing or generating a new PowerShell module, including its commands, target platforms, dependencies, and security requirements.

It helps organize reusable PowerShell code and makes requirements such as supported systems, dependencies, security, and performance explicit.

Powershell-Copilot-Standards module.instructions.md

Q: What is Powershell-Copilot-Standards module.instructions.md?

Instructions for creating PowerShell modules with a defined structure, security practices, and planned functionality. A module is a reusable package of PowerShell commands and related files.

Install

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.

agentmods

npx agentmods add instructions/fadwen/powershell-copilot-standards/module

Clone the repo

git clone --depth 1 https://github.com/fadwen/Powershell-Copilot-Standards

Made for: GitHub Copilot.

Per session 4,435 This file is loaded in full into every session.

When invoked 4,435 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.04435	$0.04435
Opus 5	$0.02218	$0.02218
Sonnet 5	$0.00887	$0.00887
Haiku 4.5	$0.00443	$0.00443

Measured yesterday against content hash abb4281f3c9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Powershell-Copilot-Standards module.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 yesterday.

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.

.github/instructions/module.instructions.md · 591 lines

How it starts

The opening of the file, as written. The whole thing — 591 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PowerShell Module Development Assistant

Create comprehensive, enterprise-grade PowerShell modules that follow organizational standards, implement security best practices, and provide scalable functionality for business operations.

Module Planning and Design

Initial Requirements Gathering

Collect essential information for module development:

Module Specifications

Module Name: Following PowerShell naming conventions (noun should be singular)
Primary Purpose: Clear business value and functional scope
Target Audience: System administrators, developers, end users, or automation systems
Functionality Scope: Core features and capabilities to implement
Dependencies: Required PowerShell modules and external systems
Security Requirements: Authentication, authorization, and data protection needs
Performance Targets: Expected load, scalability, and response time requirements

Technical Requirements

PowerShell Versions: PowerShell 7.6 (LTS, default for new modules), or 5.1 + 7.6 when the module must run on Windows estates without pwsh. Do not target 7.4/7.5 alone — both lose support 10-Nov-2026
Platform Support: Windows, Linux, macOS, or cross-platform
Integration Points: External APIs, databases, file systems, or services
Deployment Method: PowerShell Gallery, internal repository, or direct installation

Module Structure Generation

Worked example: Documentation/Examples/Module-Structure-Example is a small working module implementing everything in this section - the folder layout, the load order in ModuleExample.psm1, an explicit FunctionsToExport, a class used as a named output type, and a private helper that is never exported. Read it before generating a new module; prefer matching its shape over inventing one.

Standard Module Directory Structure

Create the complete module structure following enterprise standards:

Read the full file on GitHub · 591 lines

Changes

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.

yesterday First seen · 591 lines · 4,435 tokens per session scan A abb4281f3c9a

Subscribe to this mod's changes

Powershell-Copilot-Standards module.instructions.md is an instructions file published in the GitHub repository fadwen/Powershell-Copilot-Standards (19 stars, last pushed yesterday), licensed MIT. It adds 4,435 tokens to every session, about $0.0222 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.

Planning Security githubcopilot powershell

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/.

JanDeDobbeleer/oh-my-posh · 1,987 tokens

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.

JanDeDobbeleer/oh-my-posh · 54 tokens