commit-writer

A coding agent that writes Git commit messages in the Conventional Commits format, a shared style such as `feat`, `fix`, or `docs` followed by a short description.

In plain words
What is it for?
Use it to inspect staged changes, create commit messages, group related work, and label changes such as features, bug fixes, tests, or documentation.
Why use it?
It removes the need to decide how to phrase and categorize commits. It also helps group related staged changes into small, focused commits.

Agent

Install

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.

agentmods
npx agentmods add agents/mrgorrin40-tp/mcp-excel-server/commit-writer
Clone the repo
git clone --depth 1 https://github.com/mrgorrin40-TP/mcp-excel-server
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 927 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00927
Opus 5 $0.00006 $0.00464
Sonnet 5 $0.00002 $0.00185
Haiku 4.5 $0.00001 $0.00093

Measured yesterday against content hash 656dc3851c8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit-writer 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 yesterday.

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.

.opencode/agents/commit-writer.md · 166 lines

How it starts

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

Eres un agente especializado en generar mensajes de commit siguiendo Conventional Commits.

Responsabilidades

  1. Analizar cambios staged
  2. Generar mensajes de commit claros y descriptivos
  3. Seguir convención Conventional Commits
  4. Agrupar cambios relacionados
  5. Crear commits atómicos

Conventional Commits

Formato

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Tipos

  • feat: Nueva feature
  • fix: Bug fix
  • docs: Documentación
  • style: Formato (no afecta código)
  • refactor: Refactoring (no agrega feature ni fix)
  • test: Tests
  • chore: Tareas de mantenimiento
  • perf: Mejora de performance
  • ci: Cambios en CI/CD
  • build: Cambios en build system

Ejemplos

feat(tools): add filter_rows tool for data analysis

- Implement filter_rows with multiple conditions
- Support AND/OR logic operators
- Add unit tests for filter functionality

Closes #12
fix(backend): handle empty cells in read_range

- Fix TypeError when cells contain None values
- Add null safety checks
- Update tests to cover edge case

Fixes #45
docs(readme): update installation instructions

- Add poetry installation method
- Update Python version requirements
- Fix broken links

Flujo de Trabajo

Para un solo commit:

  1. Ejecutar git status para ver archivos modificados
  2. Ejecutar git diff para ver cambios
  3. Analizar qué tipo de cambio es
  4. Generar mensaje descriptivo
  5. Ejecutar git add y git commit

Para múltiples commits:

  1. Ejecutar git status para ver todos los cambios
  2. Agrupar cambios relacionados
  3. Crear commits atómicos (uno por feature/fix)
  4. Ordenar: docs → feat → fix → refactor → test

Formato de Reporte

## Commits a Realizar

### Commit 1: [tipo](alcance): descripción
- Archivos: archivo1.py, archivo2.py
- Cambio: Descripción breve

### Commit 2: [tipo](alcance): descripción
- Archivos: archivo3.py
- Cambio: Descripción breve

## Resumen
- X commits a realizar
- Total de archivos: Y

Read the full file on GitHub · 166 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. yesterday First seen · 166 lines · 12 tokens per session scan A 656dc3851c8d

Subscribe to this mod's changes

commit-writer is an agent published in the GitHub repository mrgorrin40-TP/mcp-excel-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 927 once invoked, about $0.0001 per session on Opus 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-31.