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.
git clone --depth 1 https://github.com/AFK-surf/OpenBridgeWrote 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/afk-surf/openbridge/commit)<a href="https://agentmods.dev/commands/afk-surf/openbridge/commit"><img src="https://agentmods.dev/badge/commands/afk-surf/openbridge/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/afk-surf/openbridge/commit"><img src="https://agentmods.dev/badge/commands/afk-surf/openbridge/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.00000 | $0.00292 |
| Opus 5.5 | $0.00000 | $0.00117 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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.
What it actually says
Using git to commit current changes with the Commit Rule following the these steps, and as fast as possible without any explanations.
Steps
- According to the staged changes existing or not,
-. If there are staged changes, read the staged changes using
git --no-pager diff --cached-. If there are not staged changes, read the changes in the current branch usinggit --no-pager diff - According to the changes content, the changes may be committed with one or more commits.
- For each commit, generate a commit message using the Commit Rule
- Commit the changes with the generated commit message
Commit Rule
Follow the commit message format: [type](scope): <message>
Format Structure
- type: Required type indicating the type of change
- scope: Optional scope in square brackets (e.g., [macos], [backend], [api])
- message: Descriptive commit message
Examples
feat(backend) Add new user authentication featurefix(macos) Fix login form validationdocs(README) Update README documentation
Rules
- Always start with an appropriate type
- Use scope in square brackets when the change affects a specific part of the codebase
- Keep the message concise but descriptive
- Use present tense ("Add feature" not "Added feature")
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 · 31 lines · 0 tokens per session scan A f7a0d6a9d083
commit is a command published in the GitHub repository AFK-surf/OpenBridge (432 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 292 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.
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.
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.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.