Borrowing it
Nothing to install: this file belongs to kasuken/github-copilot-superpowers. 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/kasuken/github-copilot-superpowers/main/.github/instructions/task-direction-approval.instructions.mdgit clone --depth 1 https://github.com/kasuken/github-copilot-superpowersWrote 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/kasuken/github-copilot-superpowers/task-direction-approval)<a href="https://agentmods.dev/instructions/kasuken/github-copilot-superpowers/task-direction-approval"><img src="https://agentmods.dev/badge/instructions/kasuken/github-copilot-superpowers/task-direction-approval/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/kasuken/github-copilot-superpowers/task-direction-approval"><img src="https://agentmods.dev/badge/instructions/kasuken/github-copilot-superpowers/task-direction-approval.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.00247 | $0.00247 |
| Opus 5.5 | $0.00099 | $0.00099 |
| Sonnet 5.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 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.
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.
- 1mo 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 (17 stars, last pushed 8mo ago), licensed MIT. It adds 247 tokens to every session, about $0.0010 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.