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/.cursor/skills/finalize-feature.mdcgit 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/rules/janekbaraniewski/openusage/finalize-feature)<a href="https://agentmods.dev/rules/janekbaraniewski/openusage/finalize-feature"><img src="https://agentmods.dev/badge/rules/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/rules/janekbaraniewski/openusage/finalize-feature"><img src="https://agentmods.dev/badge/rules/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.00033 | $0.00161 |
| Opus 5.5 | $0.00013 | $0.00064 |
| Sonnet 5.5 | $0.00007 | $0.00032 |
| Haiku 4.5 | $0.00003 | $0.00016 |
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
@docs/skills/finalize-feature/SKILL.md contains the full skill specification. Read and follow it completely.
The user's request is to finalize the feature "$ARGUMENTS".
Follow all phases in order:
- Phase 0: Pre-flight checks (build, vet, tests, scan for secrets)
- Phase 1: Create feature branch
- Phase 2: Stage and commit with conventional message
- Phase 3: Push and create PR via gh
- Phase 4: Final checklist with 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 · 17 lines · 33 tokens per session scan A 68d145477a21
finalize-feature is a cursor rule published in the GitHub repository janekbaraniewski/openusage (235 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 161 once invoked, about $0.0001 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-08-30.
Other cursor rules, from other repositories
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
git
Git rules. Conventional commits, atomic staging, no force push.
release-ts-sdk
Release @aptos-labs/ts-sdk or @aptos-labs/confidential-asset — version bump, changelog stamp, release PR, then tag + GitHub Release that triggers NPM publish.
40-git-safety
Git safety rule for branches, commits, pushes, and destructive Git commands.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
git-workflow
Git branching and PR workflow.