Borrowing it
Nothing to install: this file belongs to janekbaraniewski/openusage. 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/janekbaraniewski/openusage/main/.claude/commands/finalize-feature.mdgit clone --depth 1 https://github.com/janekbaraniewski/openusageWrote 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/janekbaraniewski/openusage/finalize-feature)<a href="https://agentmods.dev/commands/janekbaraniewski/openusage/finalize-feature"><img src="https://agentmods.dev/badge/commands/janekbaraniewski/openusage/finalize-feature/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/janekbaraniewski/openusage/finalize-feature"><img src="https://agentmods.dev/badge/commands/janekbaraniewski/openusage/finalize-feature.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.00000 | $0.00139 |
| Opus 5.5 | $0.00000 | $0.00056 |
| Sonnet 5.5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
finalize-feature 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 1mo 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.
What it actually says
Finalize the feature "$ARGUMENTS" — create branch, commit, and open PR.
Read and follow the full skill specification in docs/skills/finalize-feature/SKILL.md.
Follow all phases:
- Phase 0 — Pre-flight: Build, vet, tests pass. Check for secrets.
- Phase 1 — Branch: Create feature branch.
- Phase 2 — Commit: Draft message, show to user, stage specific files, commit.
- Phase 3 — PR: Push and create PR via
gh pr create. - Phase 4 — Checklist: Report branch, commit, PR URL.
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.
- 1mo ago First seen · 12 lines · 0 tokens per session scan A 83a37a2c5f2d
finalize-feature is a command published in the GitHub repository janekbaraniewski/openusage (235 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 139 tokens. 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
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.