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 agentmods add skills/andreaserradev-gbj/dev-workflow/dev-resumenpx skills add andreaserradev-gbj/dev-workflow --skill dev-resumegit clone --depth 1 https://github.com/andreaserradev-gbj/dev-workflowWhat 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 | $0.00062 | $0.02298 |
| Opus 5 | $0.00031 | $0.01149 |
| Sonnet 5 | $0.00012 | $0.00460 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
dev-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 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume From Checkpoint
Step 0: Discover Project Root
Run the discovery script:
bash "$DISCOVER" root
Where $DISCOVER is the absolute path to scripts/discover.sh within this skill's directory.
Path safety — shell state does not persist between tool calls, so you must provide full script paths on each call:
- Use
$HOMEinstead of the literal home directory (e.g.,bash "$HOME/code/…/discover.sh", notbash "/Users/name/…/discover.sh"). This prevents username hallucination. - Copy values from tool output. When reusing a value returned by a previous command (like
$PROJECT_ROOT), copy it verbatim from that command's output. Never retype a path from memory. - Verify on first call: if a script call fails with "No such file", the path is wrong — STOP and re-derive from the skill-loading context.
- Never ignore a non-zero exit. If any script in this skill fails, stop and report the error before continuing.
Store the output as $PROJECT_ROOT. If the command fails, inform the user and stop.
Step 1: Identify Feature to Resume
Run the discovery script to find checkpoints:
bash "$DISCOVER" checkpoints "$PROJECT_ROOT" "$ARGUMENTS"
Pass $ARGUMENTS as the third argument only if the user provided one; omit it otherwise.
- If the script exits non-zero (no
.dev/directory): inform the user, stop. - If output is empty: no checkpoints found, ask what to work on.
- If one line: use as
$FEATURE_DIR(directory containing the checkpoint). - If multiple lines: ask which feature to resume.
Never construct paths from raw $ARGUMENTS. Use only paths from script output.
After selection, validate with the validation script:
bash "$VALIDATE" checkpoint-path "$CHECKPOINT_PATH" "$PROJECT_ROOT"
Where $VALIDATE is the absolute path to scripts/validate.sh within this skill's directory. Apply the path safety rules from Step 0 ($HOME, copy from output). Outputs $FEATURE_NAME on success; on failure, STOP immediately — do not continue with an unvalidated path.
What ships with it
4 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.
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 · 171 lines · 62 tokens per session scan A f915918f2ee0
dev-resume is a skill published in the GitHub repository andreaserradev-gbj/dev-workflow (2 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 2,298 once invoked, about $0.0003 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.
Other skills, from other repositories
gsd-debug
Systematic debugging with persistent state across context resets.
gsd-code-review
Review source files changed during a phase for bugs, security issues, and code quality problems.
gsd-config
Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile.
gsd-execute-phase
Execute all plans in a phase with wave-based parallelization.
gsd-docs-update
Generate or update project documentation verified against the codebase.
gsd-ai-integration-phase
Generate an AI-SPEC.md design contract for phases that involve building AI systems.