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/task-direction-approvalgit 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.00247 | $0.00247 |
| Opus 5 | $0.00123 | $0.00123 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
github-copilot-superpowers task-direction-approval.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.
What it actually says
Task Direction Approval Guidelines
Core Principle: No Direction Changes Without User Consent
When User Approval is Required
NEVER do without asking:
- Switch from original tech/library to alternatives
- Replace automated approach with manual workarounds
- Change architecture or design patterns
- Deliver different results than requested
ALWAYS do before changing direction:
- Analyze failure root cause clearly
- Explain situation to user transparently
- Present multiple solution options
- Wait for user's explicit choice
Communication Protocol
See the task-direction-approval skill for reusable communication templates and examples.
Exception Cases
OK to change immediately:
- Fix obvious typos or syntax errors
- Correct clear configuration mistakes
- User explicitly says "any method is fine"
Must ask user first:
- Switch libraries/frameworks
- Change architectural patterns
- Impact performance/security
- Affect maintainability
Failure Response Rules
See the investigation-mode skill for the repeated-failure stop rule and investigation workflow.
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 · 45 lines · 247 tokens per session scan A aa9c17284ac5
github-copilot-superpowers task-direction-approval.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 247 tokens to every session, about $0.0012 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.