running-exploration-cycle

running-exploration-cycle is a skill for Claude Code from richfrem/agent-plugins-skills. It costs 143 tokens per session (1,134 once invoked), scanned A, original, MIT.

A coordinator for a business exploration process. It guides work from an initial interview through an approved plan, prototype work, and a handoff to engineering.

In plain words
What is it for?
Use it to start or resume an exploration session, enforce its approval gate, and route each phase to the appropriate skill.
Why use it?
It prevents later work from starting before the business plan is approved and keeps the session's progress in stored state.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Part of the agent-exploration-cycle plugin — 5 skills, 4 agents shipped together

Good fit Use it to start or resume an exploration session, enforce its approval gate, and route each phase to the appropriate skill.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/richfrem/agent-plugins-skills/running-exploration-cycle
Install

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.

Any agent
npx skills add richfrem/agent-plugins-skills --skill running-exploration-cycle
Clone the repo
git clone --depth 1 https://github.com/richfrem/agent-plugins-skills

Made for: Claude Code.

Or install agent-exploration-cycle, the plugin that ships this one along with the rest of its 5 skills, 4 agents.

Wrote 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.

agentmods badge for running-exploration-cycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/running-exploration-cycle/github.svg)](https://agentmods.dev/skills/richfrem/agent-plugins-skills/running-exploration-cycle)
Your own site
<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.

agentmods 80×15 button for running-exploration-cycle

Your own site · 80×15
<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>
Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,134 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 03f95ae75b22, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 17 executable files (scripts/check_gaps.py, scripts/dispatch.py, scripts/exploration_session.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/agent-exploration-cycle/.apm/skills/running-exploration-cycle/SKILL.md · 65 lines

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: APPROVED or ## 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.md is 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 to handing-off-to-engineering.
  • Models: never name models or prices here; choose runtime and model through the cli-agent skill.

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

  1. Resume check: run status; an in-progress session continues at its active phase (using-exploration-cycle.md).
  2. Phase 0 Intake: interview, classify, write exploration/session-brief.md (intake, brief); pick session type and dispatch (session-setup.mmd, dispatch).
  3. Phase 1 Discovery Plan: discovery-planning.md and tracks; then the capture loop in capturing-business-requirements.
  4. Phases 2 and 3: hand to building-interactive-prototypes. Phase 4: hand to handing-off-to-engineering.
  5. Each phase ends at its gate (state-and-gates.mmd); wait for the SME, then run the validator for that phase.

Read the full file on GitHub · 65 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 65 lines · 143 tokens per session scan A 03f95ae75b22

Subscribe to this mod's changes

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.

Related

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…

arcee-ai/nac · 65 tokens

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.

watt-mind/factory · 47 tokens

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.

watt-mind/factory · 45 tokens

mindforge-session-report

Generate a session report with token usage estimates, work summary, and outcomes.

sairam0424/MindForge · 19 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens