aidb: Command for Claude Code

.claude/commands/wrap.md

wrap is a command for Claude Code from ai-debugger-inc/aidb. It costs 0 tokens per session (410 once invoked), scanned A, a copy of wrap, Apache-2.0.

A command for closing out coding work with checks for linting, tests, documentation, and project guidance.

In plain words
What is it for?
Use it to run the project's wrap-up checklist, including checking code quality, tests, related documentation, and skill updates.
Why use it?
It helps catch unfinished verification or maintenance work before changes are handed over.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is ai-debugger-inc/aidb's own configuration. It tells Claude Code how to work on aidb itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aidb configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ai-debugger-inc/aidb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ai-debugger-inc/aidb/main/.claude/commands/wrap.md
Clone the repo
git clone --depth 1 https://github.com/ai-debugger-inc/aidb

Made for: Claude Code.

Wrote 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.

agentmods badge for wrap

README.md
[![agentmods](https://agentmods.dev/badge/commands/ai-debugger-inc/aidb/wrap/github.svg)](https://agentmods.dev/commands/ai-debugger-inc/aidb/wrap)
Your own site
<a href="https://agentmods.dev/commands/ai-debugger-inc/aidb/wrap"><img src="https://agentmods.dev/badge/commands/ai-debugger-inc/aidb/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.

agentmods 80×15 button for wrap

Your own site · 80×15
<a href="https://agentmods.dev/commands/ai-debugger-inc/aidb/wrap"><img src="https://agentmods.dev/badge/commands/ai-debugger-inc/aidb/wrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod 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.1 $0.00000 $0.00410
Opus 5.5 $0.00000 $0.00164
Sonnet 5.5 $0.00000 $0.00082
Haiku 4.5 $0.00000 $0.00041

Measured 2mo ago against content hash 149a68e8afdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

88% identical to wrap — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/wrap.md · 39 lines

What it actually says


description: Wrap up current work

Wrap up the current work by following the checklist below.

**NOTE: If you are low on context and/or if any of the wrap tasks are easily delegated, feel free to leverage subagents to complete the task(s) to stretch your remaining context.

Checklist:

For all changes/additions made, please:

  • Lint the code. It should pass pre-commit checks. If you find linting errors that are not related to your changes, please fix them as well, if possible.
  • Verify whether tests need updating. If so, update or add tests to cover your changes. Ensure all tests pass. Always follow existing test patterns.
  • When updating or adding new tests, ensure you re using existing fixtures and mocks where applicable. Ensure you adhere to established patterns in the given suite.
  • Check to see if there are any related docs. If there are, update them as necessary to account for the changed/added code. Do not add unimportant/minute details to documentation.
  • Check if any skills need updates (NOTE: all skill/resource docs should be <= 500 LOC):
    • NOT EVERYTHING NEEDS TO BE DOCUMENTED. Only document what is necessary for future maintainers/operators to understand the code and its usage.
    • Activate the "skill-developer" skill to assist with skill maintenance.
  • Check that proper code reuse was employed, no DRY violations were introduced, and existing codebase patterns were followed. Be wary of magic strings/numbers and use constants/enums where appropriate. Activate the "code-reuse-enforcement" skill to assist with this if needed.
  • If there are ANY actionable next steps or current problems/failures, detail them in the form of an actionable summary for the next session.

When finished, provide a commit message (without any single quotes) summarizing the changes made.

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. 2mo ago First seen · 39 lines · 0 tokens per session scan A 149a68e8afdb

Subscribe to this mod's changes

wrap is a command published in the GitHub repository ai-debugger-inc/aidb (21 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 410 tokens. A static security scan graded it A with 0 findings. It is 88% identical to wrap, differing in 22 lines, and is treated as a copy.

Related

wrap compared with commands from other repositories

wrap next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
wrapai-debugger-inc/aidbCommand215mo agoApache-2.0A0Claude Code
fire-resurrectThierryN/fire-flowCommand782mo agoMITA18Claude Code
fire-debugThierryN/fire-flowCommand782mo agoMITA16Claude Code
fire-reflectThierryN/fire-flowCommand782mo agoMITA3Claude Code
refactorSmart-AI-Memory/attune-aiCommand11yesterdayApache-2.0A12Claude Code
celigo-troubleshootceligo/aiCommand4yesterdayMITA45Claude Code
doctorMichael-OvO/obsidian-knowledge-agentCommand2064mo agoMITA21Claude Code