Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tianhanz/earsnpx agentmods add skills/tianhanz/ears/wrap-upWrote 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/tianhanz/ears/wrap-up)<a href="https://agentmods.dev/skills/tianhanz/ears/wrap-up"><img src="https://agentmods.dev/badge/skills/tianhanz/ears/wrap-up.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.00126 | $0.02499 |
| Opus 5 | $0.00063 | $0.01249 |
| Sonnet 5 | $0.00025 | $0.00500 |
| Haiku 4.5 | $0.00013 | $0.00250 |
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 6d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap Up Feature Branch
Finalize the current feature branch by discovering what changed, updating relevant documentation, committing, merging, and reporting.
The argument provided is: $ARGUMENTS
Step 1 — Understand the current state
-
Run
git branch --show-currentto get the current branch.- If
$ARGUMENTSnames a different branch, use that. - If already on the main branch, abort: "Already on the main branch — nothing to merge."
- If
-
Determine the main branch name. Check which exists:
git rev-parse --verify main 2>/dev/null && echo "main" git rev-parse --verify master 2>/dev/null && echo "master"Use whichever resolves. If both exist, prefer
main. -
List what this branch adds over main:
git log --oneline <main>..<branch> git diff --stat <main>..<branch>Show the commit list and changed-file summary to the user.
-
Check for uncommitted work:
git status git diff --statIf there are unstaged or uncommitted changes, commit them first with a descriptive message matching the repo's style (check
git log --oneline -5for conventions).
Step 2 — Discover documentation to update
Do NOT assume any specific filenames. Instead, discover what exists:
-
Find all markdown files in the repo:
find . -name '*.md' -not -path './.git/*' | sort -
Find all HTML files that look like reports or summaries (not application code):
find . -name '*.html' -not -path './.git/*' -not -path '*/node_modules/*' | sort -
From these lists, identify documentation files that are likely candidates for update. Look for files whose names or content suggest they track:
- Project status, progress, or implementation state
- Summaries or overviews of what the project contains
- Reports (especially HTML reports with timestamps)
- READMEs at any level (root, subdirectories)
-
Read each candidate file to understand its purpose and current content. Decide whether the branch's changes warrant an update to that file:
- Does the file reference features, tools, cases, or components that this branch added/changed?
- Does the file have a date or timestamp that should be refreshed?
- Does the file have a summary table, status list, or directory tree that is now stale?
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.
- 6d ago First seen · 231 lines · 126 tokens per session scan A 4a49ea8907b4
wrap-up is a skill published in the GitHub repository tianhanz/ears (5 stars, last pushed 4mo ago), licensed MIT. It adds 126 tokens to every session and 2,499 once invoked, about $0.0006 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…