Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Cmd Resume

ASecurity

Resume a previous hunt. Shows hunt history, untested endpoints, memory-informed suggestions. Usage: /resume target.com

815 stars
0 votes
0 copies
0 views
Added 5/29/2026
ai-agentspythonapi

Works with

api

Security Analysis

A100/100

Scanned 5/29/2026

$npx -y skills add H-mmer/pentest-agents --skill resume --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cmd Resume?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Cmd Resume
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/h-mmer-cmd-resume/badge)](https://www.skillsdirectory.com/skills/h-mmer-cmd-resume)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: resume
description: "Resume a previous hunt. Shows hunt history, untested endpoints, memory-informed suggestions. Usage: /resume target.com"
---

Resume hunt on: $ARGUMENTS

## What This Does
1. Read brain for target: `uv run python3 ../../tools/brain.py brief $ARGUMENTS`
2. Read brain exhausted: `uv run python3 ../../tools/brain.py exhausted $ARGUMENTS`
3. **Read chain-pending advisory**: `cat .claude/agent-memory-local/chain-pending.md 2>/dev/null` — feeder findings from prior session waiting for chain dispatch. SURFACE THESE FIRST — they have proven dollar value if chained, vs untested surface which is speculative.
4. **Generate / refresh chain plan**: `uv run python3 ../../tools/chain_plan.py $ARGUMENTS` — writes `evidence/<target>/CHAIN_PLAN.md` with 3-5 candidate next-links per pending feeder finding plus the agent to dispatch for each. Read this BEFORE picking the next vuln class — proven feeders trump speculative untested surface.
5. Read recon data from recon/ directory
6. Show what's been tested vs what remains
7. Suggest next techniques based on brain patterns

## Output
```
RESUME: target.com
═══════════════════

Brain Status:
  Confirmed findings: N
  Exhausted techniques: N
  Effective techniques: N

Untested Surface:
  1. /api/v2/users/{id}/export — not tested
  2. /api/v2/users/{id}/share — not tested
  ...

Suggestions:
  - Tech stack [X] matches pattern where IDOR was found before
  - Sibling endpoints of confirmed finding not yet tested

Actions:
  [h] /hunt target.com — resume hunting
  [s] /surface target.com — re-rank attack surface
  [r] /recon target.com — re-run recon (surface may have changed)
  [m] /monitor check — check for target changes since last session
```

## Top-Tier Resume Logic

Resume by value, not chronology.

Priority order:
1. `chain-pending` confirmed feeders with clear next link
2. validated partials needing one proof artifact
3. changed assets from `/monitor`
4. untested P1 crown-jewel endpoints
5. high-confidence class hypotheses from prior wins
6. stale recon refresh

Show what not to redo. If an area is exhausted, include the exact blocker and matrix coverage. A resumed hunt should start with a single best command, not a menu of every possible command.

Attribution

H-mmerH-mmer
View sourceSee grades on GitHubMore from H-mmer →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →