Borrowing it
Nothing to install: this file belongs to browser-use/browsercode. 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/browser-use/browsercode/main/.opencode/command/commit.mdgit clone --depth 1 https://github.com/browser-use/browsercodeWrote 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/browser-use/browsercode/commit)<a href="https://agentmods.dev/commands/browser-use/browsercode/commit"><img src="https://agentmods.dev/badge/commands/browser-use/browsercode/commit/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/browser-use/browsercode/commit"><img src="https://agentmods.dev/badge/commands/browser-use/browsercode/commit.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.00004 | $0.00163 |
| Opus 5.5 | $0.00002 | $0.00065 |
| Sonnet 5.5 | $0.00001 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
commit 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.
This is a copy
100% identical to commit — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
commit and push
make sure it includes a prefix like docs: tui: core: ci: ignore: wip:
For anything in the packages/web use the docs: prefix.
prefer to explain WHY something was done from an end user perspective instead of WHAT was done.
do not do generic messages like "improved agent experience" be very specific about what user facing changes were made
if there are conflicts DO NOT FIX THEM. notify me and I will fix them
GIT DIFF
!git diff
GIT DIFF --cached
!git diff --cached
GIT STATUS --short
!git status --short
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 · 38 lines · 4 tokens per session scan A b3e6700bfd6a
commit is a command published in the GitHub repository browser-use/browsercode (780 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 163 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to commit, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
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.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.