Borrowing it
Nothing to install: this file belongs to NomaDamas/AutoRAG-Research. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NomaDamas/AutoRAG-Research/main/.claude/commands/wrap-up.mdgit clone --depth 1 https://github.com/NomaDamas/AutoRAG-ResearchWrote 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/nomadamas/autorag-research/wrap-up)<a href="https://agentmods.dev/commands/nomadamas/autorag-research/wrap-up"><img src="https://agentmods.dev/badge/commands/nomadamas/autorag-research/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/nomadamas/autorag-research/wrap-up"><img src="https://agentmods.dev/badge/commands/nomadamas/autorag-research/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.00022 | $0.00808 |
| Opus 5 | $0.00011 | $0.00404 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrap-up -- PR Decision Summary
Analyze the current PR and post a comment summarizing:
- What problem this PR solves and how
- What key decisions the human made during the process
Step 1: Verify PR Exists
Run:
gh pr view --json number,url,title,body,headRefName,baseRefName
If fails, exit:
No PR found on the current branch. Create a PR first.
Extract PR_NUMBER, PR_URL, PR_TITLE, PR_BODY, BASE_REF.
Step 2: Gather Context
Run these in parallel:
gh pr diff --stat
git log {BASE_REF}..HEAD --pretty=format:"%h %s" --reverse
git log {BASE_REF}..HEAD --pretty=format:"%h%n%B---" --reverse
gh pr diff
git remote get-url origin
Store:
DIFF_STAT-- file change summaryCOMMIT_LOG-- one-line commit historyCOMMIT_DETAILS-- full commit messagesFULL_DIFF-- complete diffOWNER_REPO-- parsed from remote URL (handle HTTPS and SSH)
Step 3: Analyze the Session Conversation
You have access to the current conversation history. Review it carefully.
3a. Problem and Solution
- What triggered this work? (issue, bug, feature request, refactoring)
- What was the core technical challenge?
- What approach was taken?
- What are the key conceptual changes? (not a file list)
3b. Human Decisions (Human-in-the-Loop)
Scan the conversation for moments where the human:
- Chose between alternatives -- "Use A instead of B"
- Rejected a suggestion -- "No, don't do that because..."
- Added constraints -- "It must work with X", "Don't change Y"
- Made design calls -- naming, architecture, scope
- Scoped the work -- "Only do X for now", "Skip Y"
- Corrected course -- "Actually, change direction to..."
Focus on decisions that shaped the outcome. Ignore trivial approvals.
Step 4: Write the Comment
Compose in English:
## PR Wrap-up
### What problem does this PR solve and how?
**Problem**: {1-3 sentences describing the problem/motivation}
**Solution**: {2-5 sentences describing the approach and key changes. Be specific about WHAT changed and WHY.}
### Key Decisions (Human-in-the-Loop)
{List only important decisions. Each explains WHAT was decided and WHY.}
- **{decision_topic}**: {what was decided} -- {why / what was the alternative}
- ...
---
*Generated by `/wrap-up`*
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.
- 9d ago First seen · 108 lines · 22 tokens per session scan A c6ce712e49ae
wrap-up is a command published in the GitHub repository NomaDamas/AutoRAG-Research (148 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 808 once invoked, about $0.0001 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, 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.
ship
Ship is the operational release-prep flow for a connected project repo.
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.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.