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 hajekim/agentic-design-patterns-extension --skill explorationgit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-extensionWrote 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/hajekim/agentic-design-patterns-extension/exploration)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-extension/exploration"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-extension/exploration/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/hajekim/agentic-design-patterns-extension/exploration"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-extension/exploration.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.00423 | $0.04108 |
| Opus 5.5 | $0.00169 | $0.01643 |
| Sonnet 5.5 | $0.00085 | $0.00822 |
| Haiku 4.5 | $0.00042 | $0.00411 |
Grade A, and why
exploration 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.
This is a copy
100% identical to exploration — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploration & Discovery Pattern
Overview
The Exploration & Discovery Pattern enables agents to balance exploiting known-good strategies with exploring new, potentially better approaches. Agents that only exploit what worked before become stagnant — they miss improvements, can't adapt to changing environments, and plateau at local optima. Discovery-driven agents systematically explore their action space to find better solutions over time.
Core Principle: The best known solution is rarely the optimal solution — reserve capacity to discover what you don't yet know.
When This Skill Applies
Activate this pattern when:
- The agent faces multiple possible approaches with uncertain outcomes
- Known strategies may not be optimal — better methods may exist undiscovered
- The environment changes and previously good strategies may degrade
- A/B testing of agent strategies is needed to find better approaches
- Creative or novel solutions are more valuable than reliable familiar ones
- The agent must find solutions in a large, partially-unknown solution space
Rule of thumb: If the agent always does the same thing, use exploration. If it never commits to what works, use exploitation. The goal is the right balance.
Exploration-Exploitation Trade-off
The Core Dilemma
Exploit: Use the strategy that has worked best so far
→ Safe, predictable, but misses better options
Explore: Try new/less-tested strategies
→ Risky, uncertain, but may find better solutions
Balance: ε-greedy, UCB, Thompson Sampling
→ Systematic, principled trade-off
Key Algorithms
| Algorithm | Exploration Strategy | Best For |
|---|---|---|
| ε-greedy | Random with prob ε | Simple, easy to implement |
| UCB (Upper Confidence Bound) | Explore high-uncertainty options | When you can count trials |
| Thompson Sampling | Sample from belief distribution | Probabilistic rewards |
| Boltzmann Exploration | Temperature-based softmax | Graduated exploration |
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 · 440 lines · 423 tokens per session scan A b9b1e9ccea04
exploration is a skill published in the GitHub repository hajekim/agentic-design-patterns-extension (1 stars, last pushed 6mo ago), licensed MIT. It adds 423 tokens to every session and 4,108 once invoked, about $0.0017 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to exploration, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
prompt-engineering
Use this skill when asked to create, refine, analyze, or optimize prompts for Large Language Models (LLMs). This skill ensures adherence to prompt engineering best practices and enforces a rigorous design workflow.
redteam
Expertise in offensive security research, vulnerability analysis, CMS-focused application testing, and red team operations.
redteam-cms
Focused methodology for authorized CMS fingerprinting, component inventory, misconfiguration review, and vulnerability validation.
redteam-exploit-validation
Focused workflow for validating exploitability safely and turning candidate issues into reproducible, bounded proof.
redteam-recon
Focused reconnaissance workflow for authorized security assessments, bug bounty triage, lab targets, and CTF infrastructure.
redteam-reporting
Focused reporting workflow for converting verified red-team work into clear, reproducible assessment artifacts.