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 skills add tmchow/tmc-marketplace --skill implementation-wrapupgit clone --depth 1 https://github.com/tmchow/tmc-marketplaceWrote 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/skills/tmchow/tmc-marketplace/implementation-wrapup)<a href="https://agentmods.dev/skills/tmchow/tmc-marketplace/implementation-wrapup"><img src="https://agentmods.dev/badge/skills/tmchow/tmc-marketplace/implementation-wrapup.svg" alt="Measured on agentmods" 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.00046 | $0.00751 |
| Opus 5 | $0.00023 | $0.00376 |
| Sonnet 5 | $0.00009 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
implementation-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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Wrapup
Completes development with verification, optional review, and PR creation.
When to Use
- After
iterative:implementingskill completes all tasks - When you're ready to create a PR
- When you want to finish a feature branch
- Can be invoked standalone on any branch
Workflow
Phase 1: Final Verification
- Run full test suite. If tests fail, stop and report failures.
- Check for uncommitted changes — commit or stash.
Phase 2: Optional Code Review
When invoked from iterative:implementing, skip this phase — all code reviews are already complete.
When invoked standalone:
- Present an interactive choice to the user —
AskUserQuestion(Claude Code) orrequest_user_input(Codex): A) Full code review (recommended), B) Skip review. - If review: invoke
code-reviewskill (1+ rounds). - Continue when review complete or skipped.
Phase 3: Context Summary
- Determine base branch (main/master/develop).
- Check if in worktree.
- Report: N commits, files changed, branch info.
Phase 4: Present Options
Present an interactive choice to the user:
- A) Push + PR (recommended) — creates new PR, or shows existing if one exists
- B) Push only
- C) Keep branch, don't push
- D) Discard work (typed confirmation required)
Phase 5: Execute
Option A — Push + PR: Push branch with -u, run gh pr create. If PR exists, show existing PR URL. If no PR, create one following repo conventions. Return PR URL.
Option B — Push only: Push branch, report remote URL.
Option C — Keep: Report branch preserved locally.
Option D — Discard: Require typed confirmation ("discard [branch-name]"). Delete branch (and worktree if applicable).
Phase 6: Cleanup
- If in worktree and work done, offer removal.
- Switch to base branch if not in worktree.
Safeguards
- Never skip test verification - tests must pass before any option
- Never push with failing tests - stop and report failures
- Never discard without typed confirmation - require exact branch name
- git push prompts user - not pre-approved, user confirms before pushing
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.
- 7d ago First seen · 111 lines · 46 tokens per session scan A 98008279e962
implementation-wrapup is a skill published in the GitHub repository tmchow/tmc-marketplace (22 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 751 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-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.