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/CloudAI-X/opencode-workflowWrote 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/cloudai-x/opencode-workflow/commit)<a href="https://agentmods.dev/commands/cloudai-x/opencode-workflow/commit"><img src="https://agentmods.dev/badge/commands/cloudai-x/opencode-workflow/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/cloudai-x/opencode-workflow/commit"><img src="https://agentmods.dev/badge/commands/cloudai-x/opencode-workflow/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.00009 | $0.00461 |
| Opus 5.5 | $0.00004 | $0.00184 |
| Sonnet 5.5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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
Git Commit Command
Create a well-structured git commit by analyzing staged changes and generating a conventional commit message.
Phase 1: Gather Context
Run these commands in parallel to understand the current state:
git status- See all staged and unstaged changesgit diff --cached- View the actual staged changes that will be committedgit log --oneline -5- Review recent commit message style for consistency
Phase 2: Analyze Changes
Based on the staged diff, determine:
-
Change Type (use conventional commits):
feat: New featurefix: Bug fixrefactor: Code restructuring without behavior changedocs: Documentation onlytest: Adding or updating testschore: Maintenance tasksstyle: Formatting, whitespaceperf: Performance improvementci: CI/CD changes
-
Scope (optional): Affected module or component
-
Description: Concise summary focusing on WHY, not WHAT
Phase 3: Generate Commit Message
Format: type(scope): description
Rules:
- Use imperative mood ("Add feature" not "Added feature")
- Keep first line under 72 characters
- Focus on the purpose and impact
- Add body for complex changes explaining reasoning
Phase 4: Execute Commit
- If there are unstaged changes that should be included, ask user first
- Stage any additional files if requested
- Execute the commit with the generated message
- Run
git statusto verify success
Output Format
Commit Analysis
---------------
Type: [type]
Scope: [scope or "none"]
Files: [number] files changed
Generated Message:
[commit message]
Commit Status: [success/failure]
Safety Checks
- NEVER commit files that appear to contain secrets (.env, credentials, API keys)
- WARN if committing lock files or large binary files
- CONFIRM before committing if there are untracked files that might be forgotten
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 · 73 lines · 9 tokens per session scan A 1f6590fc7a7d
commit is a command published in the GitHub repository CloudAI-X/opencode-workflow (276 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 461 once invoked, about $0.0000 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.
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.