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 skills/dojogenesis/mcp/iterative-scoutingnpx skills add DojoGenesis/mcp --skill iterative-scoutinggit 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/iterative-scouting)<a href="https://agentmods.dev/skills/dojogenesis/mcp/iterative-scouting"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/iterative-scouting.svg" alt="Measured on agentmods" 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 | $0.00078 | $0.02195 |
| Opus 5 | $0.00039 | $0.01097 |
| Sonnet 5 | $0.00016 | $0.00439 |
| Haiku 4.5 | $0.00008 | $0.00219 |
Grade A, and why
iterative-scouting 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 3d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iterative Scouting Pattern Skill
Version: 1.0 Purpose: To formalize the meta-process of strategic scouting, emphasizing its iterative nature and the importance of reframing. Scouting is not a single pass -- it's a conversation with the strategic landscape.
I. The Philosophy: Scouting as a Conversation
Strategic scouting is not a linear process of finding the "right" answer. It is a conversation with the strategic landscape. The goal of the first scout is not to produce a final decision, but to generate a set of provocative routes that will elicit a deeper, more insightful response.
The real prize is not the initial answer, but the reframe of the original question.
This skill operationalizes the pattern of scout -> feedback -> reframe -> re-scout, turning a simple exploration into a powerful engine for strategic discovery. Where the strategic-scout skill handles a single pass, this skill handles the multi-pass loop that produces the deepest insights.
II. When to Use This Skill
- When facing a complex strategic decision with no obvious answer
- When the initial framing of a problem feels too narrow or binary
- After an initial strategic scout has been completed and feedback has been gathered
- When the user's feedback reveals a deeper question than the one originally asked
- When you need to teach or demonstrate the process of strategic thinking
- When the first round of scouting produced useful routes but none feel quite right
When NOT to use:
- When the first scout produced a clear winner that the user is confident about
- When the decision is time-sensitive and a second round would delay action unacceptably
- For simple, well-understood decisions that don't benefit from iteration
III. The Workflow
This is a 4-step iterative workflow. Steps 2-3 may repeat multiple times.
Step 1: Initial Scout
Goal: Explore the initial strategic tension and propose a set of viable routes.
Actions:
- Identify the initial tension (e.g., "Deprecate vs. Companion")
- Use the
strategic-scoutworkflow to explore 3-5 diverse routes - Present the routes without recommending one
- Synthesize a provocative starting point -- not to commit to, but to react against
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.
- 3d ago First seen · 216 lines · 78 tokens per session scan A 0aa8b0db68b3
iterative-scouting is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 2,195 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.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
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.
file-crdb-issue
Use when filing, creating, or reporting GitHub issues for CockroachDB. Use when asked to open a bug report, feature request, investigation issue, or performance inquiry. Also use when the user mentions wanting to track a problem, report a regression, or document unexpected behavior in CockroachDB.
engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.