Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/janekbaraniewski/openusage/finalize-featuregit clone --depth 1 https://github.com/janekbaraniewski/openusageWhat 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 | $0.00033 | $0.00161 |
| Opus 5 | $0.00016 | $0.00081 |
| Sonnet 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 2d 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.
- 2d 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 (180 stars, last pushed 9d ago), licensed MIT. It adds 33 tokens to every session and 161 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
commit-flow
Cursor rule "commit-flow" from xuliang2024/cutcli-cookbook, covering 提交流程, 提交前自检（必跑）, conventional commits, pr 流程 and ci 必过线.
final-cleanup
When the user asks for final cleanup (or similar), run the ordered fantasia-final-cleanup workflow — verify gate, docs/changelog sync, commits, push.
mojiemoji-github
Decorate Japanese GitHub Markdown with mojiemoji before posting.
git-authoring
Conventional Commit, pull-request, release-note, and PR-review conventions for this repository.
git
Git rules. Conventional commits, atomic staging, no force push.
opt-in-rule
Optional development practices rule.