Borrowing it
Nothing to install: this file belongs to jonathan-vella/apex-accelerator. 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/jonathan-vella/apex-accelerator/main/.github/instructions/powershell.instructions.mdgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/powershell)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/powershell"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/powershell/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/jonathan-vella/apex-accelerator/powershell"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/powershell.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.00952 | $0.00952 |
| Opus 5.5 | $0.00381 | $0.00381 |
| Sonnet 5.5 | $0.00190 | $0.00190 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
apex-accelerator powershell.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 6d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Scripting Guidelines
Use PowerShell 7 for maintained repository tooling. Existing Azure and Kubernetes diagnostics print human-readable evidence; governance collection writes JSON. Preserve those contracts.
Quick Reference
| Rule | Standard |
|---|---|
| Naming | Verb-Noun with approved verbs (Get-Verb), PascalCase |
| Parameters | PascalCase, singular, descriptive; use ValidateSet/ValidateNotNullOrEmpty |
| Variables | PascalCase (public), camelCase (private); avoid abbreviations |
| Aliases | Never in scripts — use full cmdlet and parameter names |
| Indentation | 4 spaces, opening { on same line as statement |
Mandatory Patterns
CmdletBinding and Comment-Based Help
Public entry scripts and exported functions need [CmdletBinding()] and comment-based help:
.SYNOPSIS, .DESCRIPTION, .PARAMETER for caller inputs, and .EXAMPLE. Use parameter
validation where meaningful. Internal helpers need comments only for non-obvious decisions.
ShouldProcess for Destructive Operations
Use SupportsShouldProcess and actually call $PSCmdlet.ShouldProcess() before destructive
or system-changing operations; choose ConfirmImpact for the consequence:
[CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = 'High')]
Return objects from reusable APIs. Keep labeled console output for diagnostic entry scripts; do not replace a machine-readable collector's JSON contract with formatted text.
Error Handling
- Fail closed for provisioning and validation: use
$ErrorActionPreference = 'Stop', catch failures at the entry boundary, emit a useful diagnostic, and exit nonzero. - Check
$LASTEXITCODEimmediately after native commands; PowerShell's error preference does not reliably turn native nonzero exit codes into terminating errors. - Best-effort diagnostic collectors may continue after individual reads fail, provided the missing evidence is visible. Do not infer a successful check from absent output.
- Use
Write-Verbosefor operational detail,Write-Warningfor warnings, avoidWrite-Hostexcept for UI text
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.
- 6d ago Changed · +32 lines · +457 tokens per session aacd33858bbc
- 1mo ago Changed · -26 lines · -117 tokens per session 0cb2df749e95
- 1mo ago First seen · 79 lines · 612 tokens per session scan A ea886f051aba
apex-accelerator powershell.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 952 tokens to every session, about $0.0038 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.