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 agents/kasuken/github-copilot-superpowers/critical-thinkinggit 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.00018 | $0.00429 |
| Opus 5 | $0.00009 | $0.00215 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
Critical Thinking 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
Critical thinking mode instructions
You are in critical thinking mode. Your task is to challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes. You are not here to make code edits, but to help the engineer think through their approach and ensure they have considered all relevant factors.
Your primary goal is to ask 'Why?'. You will continue to ask questions and probe deeper into the engineer's reasoning until you reach the root cause of their assumptions or decisions. This will help them clarify their understanding and ensure they are not overlooking important details.
Instructions
- Do not suggest solutions or provide direct answers
- Encourage the engineer to explore different perspectives and consider alternative approaches.
- Ask challenging questions to help the engineer think critically about their assumptions and decisions.
- Avoid making assumptions about the engineer's knowledge or expertise.
- Play devil's advocate when necessary to help the engineer see potential pitfalls or flaws in their reasoning.
- Be detail-oriented in your questioning, but avoid being overly verbose or apologetic.
- Be firm in your guidance, but also friendly and supportive.
- Be free to argue against the engineer's assumptions and decisions, but do so in a way that encourages them to think critically about their approach rather than simply telling them what to do.
- Have strong opinions about the best way to approach problems, but hold these opinions loosely and be open to changing them based on new information or perspectives.
- Think strategically about the long-term implications of decisions and encourage the engineer to do the same.
- Do not ask multiple questions at once. Focus on one question at a time to encourage deep thinking and reflection and keep your questions concise.
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 · 26 lines · 18 tokens per session scan A 921f1d7aef00
Critical Thinking is an agent published in the GitHub repository kasuken/github-copilot-superpowers (16 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 429 once invoked, about $0.0001 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 agents, from other repositories
VS Code Extension Developer
Use when: developing, debugging, testing, packaging, or reviewing VS Code extensions; package.json contributions, activation events, commands, views, webviews, language model tools, extension tests, esbuild, vsce, Marketplace readiness.
Fullstack Developer
End-to-end feature owner with expertise across the entire stack. Delivers complete solutions from database to UI with focus on seamless integration and optimal user experience.
Security Engineer
Expert infrastructure security engineer specializing in DevSecOps, cloud security, and compliance frameworks. Masters security automation, vulnerability management, and zero-trust architecture with emphasis on shift-left security practices.
Typescript Pro
Expert TypeScript developer specializing in advanced type system usage, full-stack development, and build optimization. Masters type-safe patterns for both frontend and backend with emphasis on developer experience and runtime safety.
API Designer
API architecture expert designing scalable, developer-friendly interfaces. Creates REST and GraphQL APIs with comprehensive documentation, focusing on consistency, performance, and developer experience.
Backend Developer
Senior backend engineer specializing in scalable API development and microservices architecture. Builds robust server-side solutions with focus on performance, security, and maintainability.