agentmods.dev

quick-commit

A command that creates a Git commit message using the Conventional Commits format, such as `fix: correct login error`. A commit is a saved set of changes in Git, a system for tracking code history.

In plain words
What is it for?
Use it to review staged changes, classify them as a feature, fix, documentation update, or other change, propose a message, and create the commit after approval.
Why use it?
It saves time choosing a commit type and writing a consistent message, while checking what is staged before committing. It stops if there is nothing staged and asks for confirmation first.

Command

121 5d ago A scan 9 tokens original Apache-2.0
View the source file LobsterTrap/lola
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 commands/lobstertrap/lola/quick-commit
Clone the repo
git clone --depth 1 https://github.com/LobsterTrap/lola
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 288 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.00009 $0.00288
Opus 5 $0.00005 $0.00144
Sonnet 5 $0.00002 $0.00058
Haiku 4.5 $0.00001 $0.00029

Measured 2d ago against content hash bf527c9226ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

quick-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 2d 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.

examples/git-module/module/commands/quick-commit.md · 38 lines

What it actually says

Create a git commit for the current staged changes.

User-provided arguments

$ARGUMENTS

Instructions

  1. Run git diff --staged to see what will be committed

  2. If there are no staged changes, inform the user and stop

  3. Analyze the changes and determine the appropriate commit type:

    • feat: A new feature
    • fix: A bug fix
    • docs: Documentation only changes
    • style: Code style changes (formatting, etc.)
    • refactor: Code change that neither fixes a bug nor adds a feature
    • test: Adding or updating tests
    • chore: Maintenance tasks

  4. Check the user-provided arguments above:

    • If a type was provided (e.g., "feat", "fix"), use it
    • If a scope was also provided (e.g., "feat api"), use both
    • If empty or not provided, infer the type from the changes

  5. Generate a concise commit message following the Conventional Commits format:

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

    Omit the scope if not applicable.

  6. Show the proposed commit message and ask for confirmation before committing

  7. Run the commit with the approved message

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. 2d ago First seen · 38 lines · 9 tokens per session scan A bf527c9226ed

Subscribe to this mod's changes

quick-commit is a command published in the GitHub repository LobsterTrap/lola (121 stars, last pushed 5d ago), licensed Apache-2.0. It adds 9 tokens to every session and 288 once invoked, about $0.0000 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-30.

Code reviewGit and workflowWriting and docsaiai-toolspackage-managerskills
Related

Other commands, from other repositories

edit-searchable

Add plugins to, or remove them from, the zero-token searchable tier.

danielLublinsky/Skill-Atlas · 14 tokens

guide

Skill navigator -- explains all installed skills and slash commands in your language. Usage: /guide (overview), /guide (deep dive), /guide (recommendation), /guide --check (dependency check), /guide --diff (compare with a skill pack).

VV1NN/skill-guide · 67 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens