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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/wrap-up)<a href="https://agentmods.dev/commands/technickai/ai-coding-config/wrap-up"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/wrap-up/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/technickai/ai-coding-config/wrap-up"><img src="https://agentmods.dev/badge/commands/technickai/ai-coding-config/wrap-up.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.00019 | $0.00680 |
| Opus 5.5 | $0.00008 | $0.00272 |
| Sonnet 5.5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
wrap-up 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 25d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrap-up - Complete the Feature Workflow
Usage
/wrap-up - Auto-detect PR from current branch
/wrap-up 123 - Wrap up PR #123
If blocked by conflicts or missing approvals, tell user what's blocking and exit.
The local branch remains - clean it up after merge:
git checkout main
git pull
git branch -d {branch-name} # Safe delete - ensures already merged
If currently in a worktree, the worktree directory persists for manual cleanup when ready.
Detect current state:
- Is this a worktree? (check
git worktree list) - What's the absolute path?
- Where's the main repo?
If in a worktree (common case after /autotask):
✓ PR #123 "Add wrap-up command" merged to main
You're in: {worktree-path} (worktree, now orphaned)
Main repo: {main-repo-path}
→ git worktree remove . (from main repo) to clean up
→ cd {main-repo-path} to continue there
If in main repo:
✓ PR #123 "Add wrap-up command" merged to main
On main at {repo-path}, up to date.
The value is clarity of state, not celebration. Brief, informative, shows next options.
Language precision: Say "merged to main" not "live" or "deployed". Merged means it's in the codebase. Live/deployed means running in production - requires CI to pass and deploy to complete. Don't conflate these.
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.
- 25d ago First seen · 97 lines · 19 tokens per session scan A 2340de871b8e
wrap-up is a command published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 19 tokens to every session and 680 once invoked, about $0.0001 per session on Opus 5.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-09-22.
Other commands, from other repositories
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…