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 skills add Vibe-Marketer/plugins-and-skills --skill strategic-thinkinggit clone --depth 1 https://github.com/Vibe-Marketer/plugins-and-skillsWrote 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/skills/vibe-marketer/plugins-and-skills/strategic-thinking)<a href="https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/strategic-thinking"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-skills/strategic-thinking/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/skills/vibe-marketer/plugins-and-skills/strategic-thinking"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-skills/strategic-thinking.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.00055 | $0.02010 |
| Opus 5 | $0.00028 | $0.01005 |
| Sonnet 5 | $0.00011 | $0.00402 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
strategic-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 9d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<quick_start> Tell me:
- What decision, problem, or situation you're facing
- What you're trying to achieve
I'll recommend the best framework and apply it, or you can choose directly from the menu below. </quick_start>
Options:
- A decision - Choosing between options
- A problem - Understanding root causes
- A situation - Strategic assessment
- Prioritization - What to focus on
- A specific framework - Apply directly
Or describe your situation and I'll recommend the best approach.
<framework_index> Available Frameworks
| Framework | Best For | Key Question |
|---|---|---|
| Pareto (80/20) | Prioritization | What 20% drives 80% of results? |
| First Principles | Innovation, stuck thinking | What's actually true vs assumed? |
| Inversion | Risk management | What would guarantee failure? |
| 5 Whys | Root cause analysis | Why does this really happen? |
| 10/10/10 | Time-horizon decisions | How will I feel in 10 min/months/years? |
| Eisenhower Matrix | Task prioritization | Urgent vs important? |
| SWOT | Strategic assessment | Strengths, weaknesses, opportunities, threats? |
| Second-Order Thinking | Consequence analysis | And then what happens? |
| Opportunity Cost | Trade-off analysis | What am I giving up? |
| Occam's Razor | Simplification | What's the simplest explanation? |
| One Thing | Focus | What single action makes everything else easier? |
| Via Negativa | Improvement through removal | What should I stop doing? |
| </framework_index> |
| If you're trying to... | Use |
|---|---|
| Decide between options with different time impacts | 10/10/10 |
| Find the root cause of a recurring problem | 5 Whys |
| Prioritize a long list of tasks | Eisenhower Matrix |
| Challenge assumptions or find new solutions | First Principles |
| Identify what could go wrong | Inversion |
| Find the simplest explanation | Occam's Razor |
| Identify the single most important action | One Thing |
| Understand what you're sacrificing | Opportunity Cost |
| Focus on what matters most | Pareto |
| Think through consequences | Second-Order Thinking |
| Assess strategic position | SWOT |
| Improve by removing rather than adding | Via Negativa |
<framework_summaries> Pareto (80/20 Rule)
Identify the vital few factors (~20%) that drive the majority of results (~80%).
Process:
- List all factors/tasks/considerations
- Estimate relative impact of each
- Rank by impact
- Identify where ~20% accounts for ~80% of impact
- Focus on vital few, deprioritize trivial many
Output: Vital Few (focus here) + Trivial Many (deprioritize)
<first_principles> First Principles Thinking
Strip away assumptions to identify fundamental truths, then rebuild from scratch.
Process:
- State the problem/belief being examined
- List all current assumptions (even "obvious" ones)
- Challenge each: "Is this actually true? Why?"
- Identify irreducible base truths
- Rebuild solution from fundamentals only
Output: Current Assumptions (challenged) + Fundamental Truths + New Possibilities </first_principles>
Instead of "How do I succeed?" ask "What would guarantee failure?" then avoid those things.
Process:
- State the goal
- Invert: What would guarantee failure?
- List all failure modes thoroughly
- For each, identify avoidance strategy
- Build success plan by avoiding failure
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.
- 9d ago First seen · 276 lines · 55 tokens per session scan A 32419927778e
strategic-thinking is a skill published in the GitHub repository Vibe-Marketer/plugins-and-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 2,010 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…