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/architecturedesign.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/architecturedesign)<a href="https://agentmods.dev/instructions/fadwen/powershell-copilot-standards/architecturedesign"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/architecturedesign/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/architecturedesign"><img src="https://agentmods.dev/badge/instructions/fadwen/powershell-copilot-standards/architecturedesign.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.01196 | $0.01196 |
| Opus 5.5 | $0.00478 | $0.00478 |
| Sonnet 5.5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
Powershell-Copilot-Standards architecturedesign.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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Architecture and Design Assistant
Help design scalable, maintainable PowerShell solutions using enterprise architecture patterns and design principles. Provide comprehensive architectural guidance from initial design through implementation.
Architecture Assessment
When reviewing or designing PowerShell solutions, evaluate and implement:
Core Architectural Principles
- Separation of Concerns: Clear separation between business logic, data access, and presentation
- Single Responsibility: Each module and function serves a specific, well-defined purpose
- Dependency Injection: Loose coupling through dependency inversion patterns
- Configuration-Driven Design: Externalized configuration for flexibility
- Event-Driven Architecture: Asynchronous communication patterns
- API-First Design: Well-defined interfaces and contracts
Design Pattern Implementation
Recommend and implement appropriate design patterns:
Factory Pattern
- Use for complex object creation scenarios
- Implement when multiple object types share common interfaces
- Provide configuration-driven object instantiation
Strategy Pattern
- Apply for algorithm selection and business rule variation
- Enable runtime behavior switching
- Support A/B testing and feature flags
Observer Pattern
- Implement for event-driven functionality
- Enable loose coupling between components
- Support monitoring and alerting scenarios
Repository Pattern
- Abstract data access layers
- Enable testability through mocking
- Support multiple data sources
Architecture Design Process
1. Requirements Analysis
Ask these key questions to understand the solution needs:
- What is the primary business purpose and value?
- What are the performance and scalability requirements?
- What security and compliance requirements apply?
- What external systems need integration?
- What is the expected user base and usage patterns?
2. Component Design
For each major component, define:
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 · 212 lines · 1,196 tokens per session scan A e00fb2cc0cb1
Powershell-Copilot-Standards architecturedesign.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 1,196 tokens to every session, about $0.0048 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.