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 DojoGenesis/mcp --skill strategic-scoutgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/strategic-scout)<a href="https://agentmods.dev/skills/dojogenesis/mcp/strategic-scout"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/strategic-scout/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/dojogenesis/mcp/strategic-scout"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/strategic-scout.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.00079 | $0.02399 |
| Opus 5 | $0.00039 | $0.01200 |
| Sonnet 5 | $0.00016 | $0.00480 |
| Haiku 4.5 | $0.00008 | $0.00240 |
Grade A, and why
strategic-scout 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Scout Skill
Version: 1.0 Purpose: To provide a structured, repeatable process for navigating strategic uncertainty, exploring multiple possible futures, and aligning on a clear, actionable direction.
I. The Philosophy: From Problem to Possibility
Strategic thinking is not about finding the right answer to a problem; it is about exploring the landscape of possibility that a tension reveals.
Three principles guide this skill:
-
Begin with a tension, not a solution. The quality of your strategic thinking is determined by the quality of your questions. A tension held open reveals more than a problem quickly solved.
-
Scouting is an act of humility. The first idea is rarely the best idea. By generating multiple routes, you resist premature commitment and let the landscape teach you what's possible.
-
Synthesis is a creative act. The best solutions often come from combining existing ideas in new ways. Routes are raw material for synthesis, not a menu to pick from.
-
Alignment is an ongoing process. Don't assume you understand the user's vision. Continuously check for alignment. The goal is a shared understanding, not a delivered answer.
II. When to Use This Skill
- At the beginning of a new project or major release
- When facing a significant strategic decision with no clear answer
- When a project feels stuck or lacks a clear direction
- When there are multiple competing priorities or stakeholder interests
- When a binary decision feels limiting (pair with
product-positioning) - When moving from "what should we build?" to exploring options before committing
When NOT to use:
- When the decision is purely tactical and well-understood
- When the user has already committed to a direction and needs execution help
- When the question can be answered with a quick lookup or factual analysis
III. The Workflow
This is a 4-step workflow for strategic scouting and decision-making.
Step 1: Identify the Tension
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 · 239 lines · 79 tokens per session scan A 52fc72aaf93e
strategic-scout is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 2,399 once invoked, about $0.0004 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
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
code-formatter
Apply repository-standard formatting to minimize diff noise and meet linter expectations.