Borrowing it
Nothing to install: this file belongs to zifeo/lade. 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/zifeo/lade/main/.cursor/skills/finalize/SKILL.mdgit clone --depth 1 https://github.com/zifeo/ladeWrote 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/zifeo/lade/finalize)<a href="https://agentmods.dev/skills/zifeo/lade/finalize"><img src="https://agentmods.dev/badge/skills/zifeo/lade/finalize/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/skills/zifeo/lade/finalize"><img src="https://agentmods.dev/badge/skills/zifeo/lade/finalize.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.00049 | $0.01082 |
| Opus 5.5 | $0.00020 | $0.00433 |
| Sonnet 5.5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
finalize 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 29d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finalize
A pageant, not a swarm. Reviewers are read-only. The parent waits, edits, then launches the next seat. One pass.
When
User says /finalize, finalize, close the MR, or ready to merge.
Do not run this on a drive-by question.
0. Sit on main first
Fetch origin/main. Rebase this branch onto it (or merge main if
rebase is refused). If the rebase conflicts, stop and ask. Do not
launch reviewers on a stale base.
Then pin what will be reviewed. Commits ahead of origin/main and
uncommitted edits both count. A dirty tree is the review subject.
Do not commit it to make a range. Stop only when both are empty.
git fetch origin main
git merge-base origin/main HEAD
git diff --stat "$(git merge-base origin/main HEAD)"
git diff --stat HEAD
Build a Spec: block for the specs child, in this order:
- Specs the user stated in this conversation
- The PR body / issue, if this is an MR
- A file the user named as the spec
If none of those exist, still launch specs. It must ask. Do not drop the seat.
The child scope uses Diff: branch changes when the commit range is
non-empty, and Diff: uncommitted changes when the work is only in
the tree. When both exist, name both.
Full Repository Path: <abs>
Diff: <branch changes | uncommitted changes | both>
Base Branch: main
Range: <merge-base>...<HEAD>
Worktree: <clean | dirty, include HEAD>
Spec:
<quoted lines, or "none, ask">
Custom agent names may be missing on the Task tool. Default path:
generalPurpose children. Paste .cursor/agents/<name>.md as the
preamble, then the scope block.
1. Parallel: bugs, simplify, specs
Launch these three together. Wait for all three. Do not launch
refactor here.
| Subagent | Job | Writes |
|---|---|---|
bugs |
Concrete failures | no |
simplify |
Smaller form, same behavior | no |
specs |
Diff vs a cited spec. Asks if no reference | no |
If specs returns Ask:, answer from this conversation or ask
the user. Then relaunch only specs once with the answer.
Do not invent product.
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.
- 29d ago Changed · +6 lines f2cd55d93856
- 1mo ago Changed 933631e111ba
- 1mo ago First seen · 124 lines · 49 tokens per session scan A 3df91c3d4d7e
finalize is a skill published in the GitHub repository zifeo/lade (136 stars, last pushed today), licensed MPL-2.0. It adds 49 tokens to every session and 1,082 once invoked, about $0.0002 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-21.
Other skills, from other repositories
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
gh-pr
This skill should be used when creating a GitHub pull request via gh pr create. Covers the gh CLI mechanics; PR title and body conventions come from the pr-style skill.
review
Review a GitHub pull request; defaults to the current branch's PR when no number is given.
pr-grooming
Use when the user wants to groom, triage, or clean up the open pull requests of a repo: "groom the PRs", "review the open PRs", "which drafts are stale", "close old draft PRs", "rebase the dependabot PRs", "are the open PRs still mergeable", "refresh that old bugfix PR", or a periodic PR review — even when they do not…
GitHub PR comment fetcher
Easily query for open discussions and reviews on a pull request to help resolve them.
review-pr
Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.