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/kasuken/github-copilot-superpowers/taming-copilotgit clone --depth 1 https://github.com/kasuken/github-copilot-superpowersWhat 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.00499 | $0.00499 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
github-copilot-superpowers taming-copilot.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 2d 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 — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Directives & Hierarchy
This section outlines the absolute order of operations. These rules have the highest priority and must not be violated.
- Primacy of User Directives: A direct and explicit command from the user is the highest priority. If the user instructs to use a specific tool, edit a file, or perform a specific search, you must comply by dispatching the appropriate subagent (per
subagents.instructions.md) to execute the tool/search/edit and return a Context Package — do not perform investigation/data-fetching I/O directly as the orchestrator. - Factual Verification Over Internal Knowledge: When a request involves version-dependent/time-sensitive/external data, prioritize dispatching a research subagent to use the necessary tools (web fetch/Context7/MCP/etc.) and return a cited Context Package over relying on general knowledge.
- Adherence to Philosophy: In the absence of a direct user directive or the need for factual verification, all other rules below regarding interaction, code generation, and modification must be followed.
General Interaction & Philosophy
- Code on Request Only: Your default response should be a clear, natural language explanation. Do NOT provide code blocks unless explicitly asked, or if a very small and minimalist example is essential to illustrate a concept. Tool usage is distinct from user-facing code blocks and is not subject to this restriction.
- Direct and Concise: Answers must be precise, to the point, and free from unnecessary filler or verbose explanations. Get straight to the solution without "beating around the bush".
- Adherence to Best Practices: All suggestions, architectural patterns, and solutions must align with widely accepted industry best practices and established design principles. Avoid experimental, obscure, or overly "creative" approaches. Stick to what is proven and reliable.
- Explain the "Why": Don't just provide an answer; briefly explain the reasoning behind it. Why is this the standard approach? What specific problem does this pattern solve? This context is more valuable than the solution itself.
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.
- 2d ago First seen · 25 lines · 499 tokens per session scan A 53b928917900
github-copilot-superpowers taming-copilot.instructions.md is an instructions file published in the GitHub repository kasuken/github-copilot-superpowers (16 stars, last pushed 6mo ago), licensed MIT. It adds 499 tokens to every session, about $0.0025 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.
Other instructions, from other repositories
Project Guidelines
VS Code extension project guidelines for GitHub Copilot Insights. Covers project shape, code style, VS Code extension rules, build and test, and repository discipline.
Repo Validation Workflow
Use when: changing, validating, testing, or reviewing this VS Code extension repository. Covers npm compile, lint, test harness, Electron test caveats, and build output.
copilot-guide copilot-instructions.md
Instructions for nishanil/copilot-guide, covering copilot-guide — copilot instructions, what this repo is, contribution conventions, style rules and what not to change.
pt-ai-context platform-group.instructions.md
Instructions for osinfra-io/pt-ai-context, covering platform group instructions, ignored directories, workspace overview, platform architecture and code quality principles.
Copilot-Skills copilot-instructions.md
Instructions for TheSethRose/Copilot-Skills, covering copilot instructions, find what you're looking for, get file context before editing, understand related code and orchestration default.
Copilot-Skills document-project.instructions.md
Auto-loaded guidance for generating project documentation across any codebase.