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.
npx agentmods add instructions/thiagoguislotti/copilot-instructions/powershell-script-creationgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWhat 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.00808 | $0.00808 |
| Opus 5 | $0.00404 | $0.00404 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
copilot-instructions powershell-script-creation.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.
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.
Purpose
Standardize PowerShell scripts in scripts/ with the same structure and safety model used by maintenance scripts.
Required Template
- Start from .github/templates/powershell-script-template.ps1 for every new script under scripts/.
- Do not assemble a final script directly from the example skeleton in this instruction; use the template as the executable starting point and treat examples here as partial guidance only.
- For AI-assisted generation prefer .github/prompts/create-powershell-script.prompt.md first, then adapt as needed.
- Start with comment-based help using SYNOPSIS, DESCRIPTION, PARAMETER, EXAMPLE, and NOTES.
- Document every script parameter with its own
.PARAMETER <Name>entry in the script help block. - Keep param block at the top of the executable body.
- Set ErrorActionPreference to Stop.
- Organize code in three sections: Helpers, Main execution, Summary/exit.
- Use descriptive function names with approved verbs.
- Add a description comment immediately above every function declaration so readers can identify purpose without reverse-engineering the implementation.
- Function description comments must explain what the function does and call out relevant parameter expectations, side effects, or returned value when the behavior is not obvious from the signature alone.
Template Placeholder Mapping
- Replace [SHORT_SCRIPT_SUMMARY] with one-line script intent.
- Replace [DETAILED_SCRIPT_DESCRIPTION] with operational behavior and scope.
- Replace [AREA] and [SCRIPT_NAME] examples with concrete script path.
- Replace [RELATIVE_TARGET_PATH] with the primary resource path used by script logic.
- Keep helper function names unless there is a clear context-specific reason to rename them.
Root Detection
- Detect repository root automatically when script behavior depends on repo layout.
- Accept optional RepoRoot parameter; validate with Resolve-Path.
- Prefer a shared helper named Set-CorrectWorkingDirectory or equivalent deterministic logic.
- Never assume caller current directory is the repository root.
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 · 85 lines · 808 tokens per session scan A 6238f23d5537
copilot-instructions powershell-script-creation.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 808 tokens to every session, about $0.0040 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-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.