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.
git clone --depth 1 https://github.com/jpeseWang/solo-dev-workflowWrote 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.
[](https://agentmods.dev/commands/jpesewang/solo-dev-workflow/wrap)<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/wrap"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/wrap/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.
<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/wrap"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/wrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00635 |
| Opus 5.5 | $0.00000 | $0.00254 |
| Sonnet 5.5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 2mo 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 — 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. 🎉
====================================
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.
- 2mo ago First seen · 84 lines · 0 tokens per session scan A 4e7142b2d3ac
wrap is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 2mo 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.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.