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-wrapupnpx skills add andreaserradev-gbj/dev-workflow --skill dev-wrapupgit 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.00045 | $0.04622 |
| Opus 5 | $0.00023 | $0.02311 |
| Sonnet 5 | $0.00009 | $0.00924 |
| Haiku 4.5 | $0.00005 | $0.00462 |
Grade A, and why
dev-wrapup 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Wrap-Up
Review the current session for learnings worth persisting and self-improvement signals.
REVIEW-ONLY MODE
This skill analyzes and suggests. It does NOT apply changes without explicit user confirmation.
- Do NOT write to any file until the user confirms specific items
- Do NOT create new files unless the user approves
- Present all findings for review, then wait for confirmation before each application step
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.
Analyze Session
Step 1: Read Existing Documentation
Before analyzing, read these files to avoid surfacing items already documented:
$PROJECT_ROOT/CLAUDE.md(or equivalent project docs:AGENTS.md,GEMINI.md) — whichever exists, store its name as$PROJECT_DOCSfor use in routing targets later$PROJECT_ROOT/.claude/rules/(or equivalent scoped rules directory) — if it exists, read all files in the directory; store the path as$SCOPED_RULES_DIR$PROJECT_ROOT/CLAUDE.local.md(or equivalent personal project docs) — if it exists, store its path as$PERSONAL_PROJECT_DOCS~/.claude/CLAUDE.md(or equivalent user global docs) — if it exists, store its path as$USER_GLOBAL_DOCS
What ships with it
1 file 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 · 364 lines · 45 tokens per session scan A b033e7cca81e
dev-wrapup is a skill published in the GitHub repository andreaserradev-gbj/dev-workflow (2 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 4,622 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.
Other skills, from other repositories
gsd-debug
Systematic debugging with persistent state across context resets.
gsd-config
Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile.
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items.