opencode-gui: Command for Claude Code

.agents/commands/commit.md

commit is a command for Claude Code from saffron-health/opencode-gui. It costs 16 tokens per session (749 once invoked), scanned A, original, MIT.

A Git command workflow that reviews all current changes, stages them, creates a conventional commit message, and commits them.

In plain words
What is it for?
Use it after making code changes when you want to inspect the affected files, stage everything, and create a commit such as feat, fix, refactor, docs, or chore.
Why use it?
It reduces the manual work of checking edits, choosing a commit description, and preparing the changes for version history.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents).

This is saffron-health/opencode-gui's own configuration. It tells Claude Code how to work on opencode-gui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opencode-gui configures →

Reuse

Borrowing it

Nothing to install: this file belongs to saffron-health/opencode-gui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/saffron-health/opencode-gui/main/.agents/commands/commit.md
Clone the repo
git clone --depth 1 https://github.com/saffron-health/opencode-gui

Made for: Claude Code.

Wrote 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.

agentmods badge for commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/saffron-health/opencode-gui/commit/github.svg)](https://agentmods.dev/commands/saffron-health/opencode-gui/commit)
Your own site
<a href="https://agentmods.dev/commands/saffron-health/opencode-gui/commit"><img src="https://agentmods.dev/badge/commands/saffron-health/opencode-gui/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.

agentmods 80×15 button for commit

Your own site · 80×15
<a href="https://agentmods.dev/commands/saffron-health/opencode-gui/commit"><img src="https://agentmods.dev/badge/commands/saffron-health/opencode-gui/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 749 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00749
Opus 5.5 $0.00006 $0.00300
Sonnet 5.5 $0.00003 $0.00150
Haiku 4.5 $0.00002 $0.00075

Measured 2mo ago against content hash c70b36668a6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.agents/commands/commit.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Automatically stage all changes and commit with an appropriate message based on the changes made. Shows a summary of what files were changed and how.

Steps

  1. Show current status before staging:

    git status --porcelain
    
  2. Stage all changes:

    git add .
    
  3. Get changed files for analysis:

    git diff --cached --name-only
    
  4. Get detailed change summary:

    git diff --cached --stat
    
  5. Analyze changes to create commit message:

    • Read the changed files to understand the scope of changes
    • Look for spec files in specs/ directory that might be related to these changes
    • Focus on the main functional changes rather than minor refactoring
    • Create a concise, descriptive commit message following conventional commit format
    • Consider these patterns:
      • feat: add new feature
      • fix: resolve bug in component
      • refactor: reorganize utility functions
      • docs: update documentation
      • chore: update dependencies
  6. Commit the changes:

    git commit -m "Generated commit message"
    
  7. Show commit summary:

    git show --stat --oneline HEAD
    

Analysis Guidelines

Commit Message Format

  • Use conventional commit format: type: description
  • Keep it concise and descriptive
  • Focus on what the change accomplishes, not how it was done
  • Use imperative mood: "add" not "added"

Change Analysis Priority

  1. Spec files: New/modified files in specs/ indicate major features
  2. Core functionality: API endpoints, UI components, database schemas
  3. Configuration: Build, dependency, or environment changes
  4. Documentation: README, AGENT.md, or other doc updates
  5. Refactoring: Code reorganization without functional changes

Example Output

Files staged for commit:
 M apps/web/src/components/TaskList.tsx
 A specs/task-filters.md
 M packages/ui/src/Button.tsx
 D apps/web/src/old-component.tsx

Changes summary:
 apps/web/src/components/TaskList.tsx | 15 ++++++++++++---
 specs/task-filters.md                | 42 +++++++++++++++++++++++++++++++++++++++
 packages/ui/src/Button.tsx           |  8 ++++----
 apps/web/src/old-component.tsx       | 23 -----------------------
 4 files changed, 58 insertions(+), 26 deletions(-)

Committed: feat: add task filtering functionality
[main abc1234] feat: add task filtering functionality
 4 files changed, 58 insertions(+), 26 deletions(-)

Read the full file on GitHub · 113 lines

Changes

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.

  1. 2mo ago First seen · 113 lines · 16 tokens per session scan A c70b36668a6f

Subscribe to this mod's changes

commit is a command published in the GitHub repository saffron-health/opencode-gui (58 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 749 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.