Resume

Resume is a skill for Claude Code from Nagiliant/Genesis-Legacy-V2. It costs 37 tokens per session (598 once invoked), scanned A, original, Apache-2.0.

A read-only way to reconstruct where a structured development pipeline stopped. It examines approval records, project state, completed work, failed approaches, recent notes, and uncommitted files.

In plain words
What is it for?
Use it after stepping into an existing project to identify the active feature, the next unapproved phase or specification, partial work, and the next action.
Why use it?
It removes the guesswork when returning to unfinished work and helps avoid repeating approaches that already failed.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the genesis-spec-kit plugin — 23 skills shipped together

Good fit Use it after stepping into an existing project to identify the active feature, the next unapproved phase or specification, partial work, and the next action.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nagiliant/genesis-legacy-v2/genesis-resume
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 Nagiliant/Genesis-Legacy-V2 --skill genesis-resume
Clone the repo
git clone --depth 1 https://github.com/Nagiliant/Genesis-Legacy-V2

Made for: Claude Code.

Or install genesis-spec-kit, the plugin that ships this one along with the rest of its 23 skills.

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 Resume

README.md
[![agentmods](https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-resume/github.svg)](https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-resume)
Your own site
<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-resume"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-resume/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 Resume

Your own site · 80×15
<a href="https://agentmods.dev/skills/nagiliant/genesis-legacy-v2/genesis-resume"><img src="https://agentmods.dev/badge/skills/nagiliant/genesis-legacy-v2/genesis-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 598 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.00037 $0.00598
Opus 5 $0.00018 $0.00299
Sonnet 5 $0.00007 $0.00120
Haiku 4.5 $0.00004 $0.00060

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

Security

Grade A, and why

Resume 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 12d 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.

skills/genesis-resume/SKILL.md · 54 lines

How it starts

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

Resume — Pick Up Where I Left Off

The "I just got here — what's happening?" command. Reconstructs the pipeline position from disk, loads only the active group's state and the frontier (next) spec in full, lists failed approaches not to retry, and presents the next action. Read-only — never writes approval records.

Inputs

  • approvals/master.json + the one active group-{N}.json (max two approval files)
  • .genesis/project-state.md (active feature + mode)
  • units.json (lowfield)
  • tried.json (failed approaches), filtered to the frontier spec
  • The most recent journal entry under journal/ (for absence sizing)
  • git status (uncommitted work)

Process

  1. Determine the feature (argument, else the active feature from project-state.md; if several, ask).
  2. Read approval state: build a map of approved phases, complete groups, implemented specs.
  3. Find the frontier — the first unapproved item in pipeline order: master phases (brainstorm → feature → specify → clarify → northstar), then groups in order, within a group its specs in order, then per-group audits A1–A5, then the F-pass.
  4. Check for partial work at the frontier: implementation files present but no approval, uncommitted git changes, logged failed approaches.
  5. Load context efficiently: distilled summaries for completed groups/specs, full content only for the frontier spec.
  6. Present the tried log for the frontier spec ("Do NOT retry: {approach} — failed because {reason}").
  7. Compose an absence-aware briefing sized by time since the last journal entry (<4h brief, 4–24h one sentence, 1–7 days 3–5 sentences, 7+ days full), state the tier and why, then present the next action.

Output

RESUME: <feature>
Feature phase: <status> (<phases> approved)
Groups: N/total complete
Active group: N (<title>)   Active spec: <spec-id> (<title>)
Status: clean|partial — <detail>
Tried: N approaches logged (<summary>)
Next: <next pipeline action>

Mode differences

Brownfield adds a scope reminder (files in scope) and regression notes. Lowfield adds a unit-progress summary and the next unit action.

Read the full file on GitHub · 54 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.

  1. 12d ago First seen · 54 lines · 37 tokens per session scan A 9c3c620130ac

Subscribe to this mod's changes

Resume is a skill published in the GitHub repository Nagiliant/Genesis-Legacy-V2 (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 598 once invoked, about $0.0002 per session on Opus 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-08-31.

Related

Other skills, from other repositories

auth-doctor

Diagnose and fix issues in existing auth setups. Scans environment, files, security, middleware, OAuth, database, and dangerous code patterns. Produces scored health report with actionable fixes.

ShipWithAI/shipwithai-plugins · 42 tokens

init

Set up the Claude Code harness for this project. Configures CLAUDE.md, permissions, hooks, MCP servers, agents, and SSOT docs based on your stack and chosen tier. Run on first setup or when CLAUDE.md is missing or has [PLACEHOLDER] markers. Trigger phrases: "set up harness", "configure claude", "onboard project"…

ShipWithAI/shipwithai-plugins · 96 tokens

new-project

Start a new project from scratch. 3-phase interview: project goals → tech stack → architecture → conventions. Scaffolds using official tools then configures the Claude Code harness. Run on an empty directory. Trigger phrases: "start a new project", "create project from scratch", "greenfield setup", "I have an empty…

ShipWithAI/shipwithai-plugins · 78 tokens

setup-memory

Configure project memory: write CLAUDE.md with architecture context and (Tier 3) set up a self-sustaining .claude/memory/ lifecycle — SessionStart load hook, Stop save-nudge hook, and a /save-memory skill that distills each session. Called by init or standalone to configure the memory pillar. Trigger phrases: "setup…

ShipWithAI/shipwithai-plugins · 89 tokens

optimize-harness

Analyze Claude Code tool call logs and suggest harness improvements based on actual usage patterns. Requires observability enabled + 7 days of data. Trigger phrases: "optimize harness", "harness suggestions", "improve my setup", "analyze tool usage", "what hooks should I add".

ShipWithAI/shipwithai-plugins · 64 tokens

setup-skills

Install reusable project skills into .claude/skills/. Ships git-workflow (commit/branch/PR conventions from your init choices). Triggers: "setup skills", "install project skills", "add git skill".

ShipWithAI/shipwithai-plugins · 48 tokens