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 commands/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.00000 | $0.00139 |
| Opus 5 | $0.00000 | $0.00069 |
| Sonnet 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 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
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.
- 2d ago First seen · 12 lines · 0 tokens per session scan A 83a37a2c5f2d
finalize-feature is a command published in the GitHub repository janekbaraniewski/openusage (180 stars, last pushed 8d ago), 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
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
ship
Commit all changes, push branch, create/update PR, and run local validation.
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
ship
Create a new git branch, commit changes, and create a pull request.
push-pr
Commit, push, and open a PR.
commit-push-pr
現在のブランチに対して変更をコミットし、リモートへプッシュしたあと、Pull Request を作成するための一括実行コマンドの例です。 main/master への直接プッシュ禁止や、コミット前に実行する品質チェック（lint / test / build など）、PR 作成フロー（AI/MCP を使うか、CLI を使うかなど）は、各プロジェクトのポリシーに応じてこのテンプレートを調整してください。.