wrap

An end-of-task command that records completed work in TASKS.md and CHANGELOG.md, two project files used to track work and releases.

In plain words
What is it for?
Use it to identify what shipped from the current branch, mark the matching task done, and add a short unreleased change entry.
Why use it?
It leaves a lasting record without requiring a separate ticketing service or time-tracking system.

Command

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.

agentmods
npx agentmods add commands/jpesewang/solo-dev-workflow/wrap
Clone the repo
git clone --depth 1 https://github.com/jpeseWang/solo-dev-workflow
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 635 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00635
Opus 5 $0.00000 $0.00318
Sonnet 5 $0.00000 $0.00127
Haiku 4.5 $0.00000 $0.00064

Measured yesterday against content hash 4e7142b2d3ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wrap 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 yesterday.

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.

variants/solo/commands/wrap.md · 84 lines

How it starts

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

Wrap up

Close the task: mark it done in TASKS.md, append a CHANGELOG entry, and summarize what shipped.

The lightweight end-of-task ritual that replaces a ticket system. Leaves a durable trail in two committed files — no external service, no time accounting.

Input: optional. If the current branch maps to a TASKS.md entry, use that; otherwise ask which task this wraps (or summarize from the branch's commits).


Step 1 — Figure out what shipped

BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null || true)   # empty when detached
BASE="${BASE_BRANCH:-main}"
git log "origin/$BASE..HEAD" --pretty=format:"- %s" 2>/dev/null || git log -10 --pretty=format:"- %s"

Summarize the change in one line a user (or future you) would understand — not a restatement of the commit subjects, the actual outcome ("Reports can now be exported to CSV").

Step 2 — Update TASKS.md

Move the active entry to the Done section, check it off, and stamp the finish date:

- [x] **{title}** — `{branch}` — {start date} → {YYYY-MM-DD}

If there was no TASKS.md entry (the change skipped /plan), add it straight to Done.

Step 3 — Append to CHANGELOG.md

Add a line under ## [Unreleased], grouped by kind (Keep a Changelog style). Create the file from the template if missing.

## [Unreleased]
### Added
- {user-facing summary}        # for feat
### Fixed
- {user-facing summary}        # for fix
### Changed
- {user-facing summary}        # for refactor/behavior change

Only log what's worth a reader's attention — internal chores/tests usually don't need an entry.

Step 4 — Commit the bookkeeping

git add TASKS.md CHANGELOG.md
git commit -m "docs: update tasks and changelog"

(If the PR is already merged and you're on main, commit there; otherwise this rides along on the branch — your call. Mention which you did.)

Output

====================================
WRAP
====================================
Task:      {title}  → done
Shipped:   {one-line outcome}
CHANGELOG: + entry under [Unreleased] / {section}
TASKS.md:  moved to Done

Open tasks remaining: {n}
====================================
Done. 🎉
====================================

Read the full file on GitHub · 84 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. yesterday First seen · 84 lines · 0 tokens per session scan A 4e7142b2d3ac

Subscribe to this mod's changes

wrap is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 635 tokens. 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.