What is step-through?

An interactive guide for working through a long numbered answer one item at a time, recording a decision for each item.

Walking through recommendations, findings, or task lists, choosing an action per item, and saving progress so an interrupted review can continue later.

It makes large reviews easier to manage and helps apply consistent choices to similar issues over time.

step-through — Skill for Claude Code by mostafa-drz

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 mostafa-drz/claude-skills --skill step-through

Clone the repo

git clone --depth 1 https://github.com/mostafa-drz/claude-skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/step-through/github.svg)](https://agentmods.dev/skills/mostafa-drz/claude-skills/step-through)

Your own site

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/step-through"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/step-through/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/step-through"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/step-through.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,947 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00004	$0.03947
Opus 5	$0.00002	$0.01973
Sonnet 5	$0.00001	$0.00789
Haiku 4.5	$0.00000	$0.00395

Measured 10d ago against content hash 77333bd74c90, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

step-through scanned grade B with 1 finding 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 10d 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

7. **Learn quietly.** Promote a rule only after 3+ consistent feedback signals. Mention once when promoting, never lecture. Demote unstable rules instead of accumulating clutter.

code/step-through/SKILL.md · 336 lines

How it starts

The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/step-through

Take a long enumerated response and walk through it interactively, one item at a time, with a decision per item — and learn the user's per-severity habits over sessions.

Preferences

On startup, use the Read tool to load ~/.claude/skills/step-through/preferences.md. If missing, treat as first-run (see First-time detection below).

Defaults when no preferences exist:

default-depth: concise — one paragraph plus 1–2 references on dive deeper
show-outline: yes — print the outline before starting
persist-session-log: yes — append decisions to sessions/<date>.md
auto-pick-source: most-recent — most recent enumerated assistant message
action-confirmation: destructive-only — confirm before file deletes / branch ops / pushes / external posts; everything else proceeds
resume-on-stop: yes — when a session is stopped mid-way, save resume state so the next invocation can pick up where it left off
per-severity-defaults: none yet (filled by Learned over time)

Context

Do NOT pre-load anything on startup. The skill works against the current conversation's recent assistant messages. Run Bash/Read only when the user picks "dive deeper" or "take action" on a specific item — at that point, fetch only what's needed for that item.

Command routing

Check $ARGUMENTS:

help → display help, then stop
config → interactive setup, then stop
reset → delete ~/.claude/skills/step-through/preferences.md AND feedback-journal.md AND sessions/, confirm, stop
feedback → collect thumbs-up/down on the most recent walkthrough (see Feedback & learning), stop
resume → continue the most recent stopped walkthrough using saved resume state, stop if none
anything else (including empty) → run the skill

Help

/step-through — Walk through a long enumerated response item-by-item

Usage:
  /step-through                    Walk through the most recent enumerated response
  /step-through --filter blockers  Only walk through items in that section/severity
  /step-through --start 3          Resume from item N
  /step-through --from "<hint>"    Pick a different message by short description
  /step-through resume             Continue the most recent stopped walkthrough
  /step-through feedback           Rate the last walkthrough (improves future defaults)
  /step-through config             Set preferences
  /step-through reset              Clear preferences + feedback journal + sessions
  /step-through help               This help

Per-item options:
  Dive deeper        Pull code / docs / context to better understand
  Take action        Edit, run, research, or fix right now
  Note & defer       Capture decision (e.g. "address with AIS-XXXX"), move on
  Skip               Drop without action
  Stop               End the walkthrough, summarise

Examples:
  /step-through                              After a long PR review
  /step-through --filter blockers            Only critical items
  /step-through --start 7                    Resume mid-list

Current preferences:
  (loaded from ~/.claude/skills/step-through/preferences.md)

Read the full file on GitHub · 336 lines

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.

10d ago First seen · 336 lines · 0 tokens per session scan B 77333bd74c90

Subscribe to this mod's changes

step-through is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 27d ago), licensed MIT. It adds 4 tokens to every session and 3,947 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Productivity ai-tools automation claude claude-skills developer-tools

hydra

Fan multiple independent tasks out to SEPARATE Terminal.app windows, each running its own live claude session with exactly the context it needs — real parallel sessions with isolated context windows, not subagents. Confirms grouping/model/risk with the user before launching, delivers context invisibly, auto-tiles…

SpoiledMilkLabs/skills · 139 tokens

shipkit-work-memory

Log session progress and save resume state. Infers from conversation and git. Triggers: 'log progress', 'session summary', 'checkpoint', 'save progress', 'end session'.

stefan-stepzero/shipkit · 42 tokens

session-update

Use when the user says "update session", "log progress", "checkpoint session", or invokes /session-update — especially before /clear or handoff.

jkm-4314/claude-code-skills · 33 tokens

interview-kit-builder

Generate a complete structured interview kit for a role — 3-5 role-specific competencies, one behavioral (STAR-format) question per competency, 1-5 scoring rubric with explicit behavioral anchors at each level, per-panel scorecards, interviewer debrief template.

tinh2/skills-hub-registry · 57 tokens

codex-symphony

Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.

citedy/skills · 61 tokens

claudeshrink

Automatically compress large natural text or log files before processing. Trigger when the user pastes massive text blobs, or asks to analyze a large file (logs, docs, transcripts), or provides a prompt that is too large for the context window. DO NOT trigger on source code files or structural data (JSON, XML).

g-akshay/ClaudeShrink · 68 tokens

step-through