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 richfrem/agent-plugins-skills --skill running-exploration-cyclegit clone --depth 1 https://github.com/richfrem/agent-plugins-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/richfrem/agent-plugins-skills/running-exploration-cycle)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/running-exploration-cycle"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/running-exploration-cycle/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/richfrem/agent-plugins-skills/running-exploration-cycle"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/running-exploration-cycle.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.00143 | $0.01134 |
| Opus 5.5 | $0.00057 | $0.00454 |
| Sonnet 5.5 | $0.00029 | $0.00227 |
| Haiku 4.5 | $0.00014 | $0.00113 |
Grade A, and why
running-exploration-cycle 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running the Exploration Cycle
Front door and conductor of the exploration plugin. Process: process-overview.mmd and process-definition.md.
Contents
Constraints
- HARD-GATE: no capture, prototype or handoff work until the SME has approved the Discovery Plan (
PLAN_STATUS: APPROVEDor## SME Approval); a DRAFT never counts. Use the redirect in hard-gate-enforcement.md verbatim, offer no workaround. - State: the SQLite state engine is authoritative;
exploration/exploration-dashboard.mdis a read-only projection. Never rely on conversation memory for a gate. If you were dispatched as a subagent, skip this skill. - One question at a time, in the SME's business language (no git, branch or subagent jargon).
- Routing: an existing working prototype goes to
reengineering-vibe-code; technical codebase discovery goes tohanding-off-to-engineering. - Models: never name models or prices here; choose runtime and model through the
cli-agentskill.
Quick start
Run from this skill's folder, with CLAUDE_PROJECT_DIR set to the project:
python3 scripts/state_engine.py status
python3 scripts/validate_phase_gate.py 1
python3 scripts/check_gaps.py --files exploration/captures/brd-draft.md --threshold 3
Workflow
- Resume check: run
status; an in-progress session continues at its active phase (using-exploration-cycle.md). - Phase 0 Intake: interview, classify, write
exploration/session-brief.md(intake, brief); pick session type and dispatch (session-setup.mmd, dispatch). - Phase 1 Discovery Plan: discovery-planning.md and tracks; then the capture loop in
capturing-business-requirements. - Phases 2 and 3: hand to
building-interactive-prototypes. Phase 4: hand tohanding-off-to-engineering. - Each phase ends at its gate (state-and-gates.mmd); wait for the SME, then run the validator for that phase.
What ships with it
47 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/exploration-dashboard.md 1.8 KB
- evals/evals.json 6.0 KB
- references/acceptance-criteria.md 2.2 KB
- references/architecture.md 6.3 KB
- references/design-rationale.md 6.3 KB
- references/discovery-planning-agent.md 4.7 KB
- references/discovery-planning-tracks.md 5.9 KB
- references/discovery-planning.md 2.4 KB
- references/dispatch-strategies.md 5.7 KB
- references/domain-patterns-exploration-session.md 3.3 KB
- references/domain-patterns.md 1.7 KB
- references/environment-check.md 1.7 KB
- references/exploration-cycle-orchestrator-agent.md 17 KB
- references/exploration-optimizer.md 8.9 KB
- references/exploration-orchestrator-guide.md 3.7 KB
- references/exploration-session-brief.md 2.1 KB
- references/exploration-workflow.md 2.4 KB
- references/hard-gate-enforcement.md 3.3 KB
- references/high-level-process.mmd 885 B
- references/intake-agent.md 12 KB
- references/orchestrator-loop.mmd 1.3 KB
- references/post-run-survey.md 1.7 KB
- references/problem-framing-agent.md 2.7 KB
- references/process-definition.md 3.7 KB
- references/process-overview.mmd 3.7 KB
- references/session-setup.mmd 1.3 KB
- references/state-and-gates.mmd 1.0 KB
- references/using-exploration-cycle.md 2.3 KB
- requirements-dev.in 69 B
- requirements.in 60 B
- scripts/check_gaps.py 2.5 KB runs code
- scripts/dispatch.py 24 KB runs code
- scripts/exploration_session.py 16 KB runs code
- scripts/sandbox_runner.py 8.7 KB runs code
- scripts/smoke_test.py 5.1 KB runs code
- scripts/state_engine.py 22 KB runs code
- scripts/test_dispatch_authorization_gate.py 4.0 KB runs code
- scripts/test_dispatch_security.py 10.0 KB runs code
- scripts/test_exploration_integration.py 15 KB runs code
- scripts/test_integration.py 4.4 KB runs code
- scripts/test_path_traversal.py 1.8 KB runs code
- scripts/test_phase_premium_counter.py 2.0 KB runs code
- scripts/test_sandbox_runner.py 5.6 KB runs code
- scripts/test_session_start_hook.py 2.4 KB runs code
- scripts/test_state_engine.py 14 KB runs code
- scripts/test_validate_phase_gate.py 13 KB runs code
- scripts/validate_phase_gate.py 8.7 KB runs code
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 · 65 lines · 143 tokens per session scan A 03f95ae75b22
running-exploration-cycle is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 1,134 once invoked, about $0.0006 per session on Opus 5.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-10-24.
Other skills, from other repositories
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
mindforge-session-report
Generate a session report with token usage estimates, work summary, and outcomes.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.