cog: Command for Claude Code

.claude/commands/commit.md

commit is a command for Claude Code from marciopuga/cog. It costs 38 tokens per session (754 once invoked), scanned A, original, MIT.

A command workflow for creating Git commits, which are saved snapshots of project changes, using a standard message format. It also checks for secrets and generated files before staging selected files.

In plain words
What is it for?
Use it to review the working tree, stage specific files, write Conventional Commit messages such as `fix:` or `feat:`, and create a guarded commit.
Why use it?
It reduces the chance of committing passwords, keys, build output, dependencies, or unrelated changes by mistake.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is marciopuga/cog's own configuration. It tells Claude Code how to work on cog 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 cog configures →

Reuse

Borrowing it

Nothing to install: this file belongs to marciopuga/cog. 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/marciopuga/cog/main/.claude/commands/commit.md
Clone the repo
git clone --depth 1 https://github.com/marciopuga/cog

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/marciopuga/cog/commit/github.svg)](https://agentmods.dev/commands/marciopuga/cog/commit)
Your own site
<a href="https://agentmods.dev/commands/marciopuga/cog/commit"><img src="https://agentmods.dev/badge/commands/marciopuga/cog/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/marciopuga/cog/commit"><img src="https://agentmods.dev/badge/commands/marciopuga/cog/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 754 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.00038 $0.00754
Opus 5.5 $0.00015 $0.00302
Sonnet 5.5 $0.00008 $0.00151
Haiku 4.5 $0.00004 $0.00075

Measured 2mo ago against content hash 691e31e0a398, 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.

.claude/commands/commit.md · 66 lines

How it starts

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

Use this skill when the user wants to commit changes to git. Trigger if the user says "commit", "save changes", "commit this", or asks to create a git commit. Examples: "commit", "commit and push", "save my changes".

Process

  1. Assess the working tree — Run git status (never use -uall) and git diff --staged and git diff to understand what changed.

  2. Guard rails — Before staging:

    • Never commit files that contain secrets (.env, credentials, tokens, keys). Warn if any are present.
    • Never commit build artifacts (dist/, *.tsbuildinfo).
    • Never commit node_modules/.
    • If there are no changes to commit, say so and stop.
  3. Stage selectively — Stage files by name. Prefer git add <file>... over git add -A or git add . to avoid accidentally including sensitive or unrelated files. Group related changes — if unrelated changes exist, ask whether to commit everything together or separately.

  4. Write the commit message — Use Conventional Commits format:

    • feat: new feature
    • fix: bug fix
    • refactor: code restructuring without behavior change
    • chore: maintenance, dependencies, config
    • docs: documentation only
    • style: formatting, whitespace
    • test: adding or updating tests
    • Scope is optional: feat(whatsapp): add voice note transcription
    • Subject line: imperative mood, lowercase, no period, under 72 chars
    • Body (if needed): blank line after subject, wrap at 72 chars, explain why not what
    • If you are an AI agent, end with a co-author trailer identifying yourself, e.g. Co-Authored-By: Claude <[email protected]> — use your actual model/agent identity, don't hardcode someone else's
  5. Commit — Use a HEREDOC for the message to preserve formatting:

    git commit -m "$(cat <<'EOF'
    type(scope): subject line
    
    Optional body explaining why.
    
    Co-Authored-By: <your agent identity> <[email protected]>
    EOF
    )"
    
  6. Verify — Run git status after committing to confirm success. Show the resulting git log --oneline -1.

Read the full file on GitHub · 66 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 · 66 lines · 38 tokens per session scan A 691e31e0a398

Subscribe to this mod's changes

commit is a command published in the GitHub repository marciopuga/cog (377 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 754 once invoked, about $0.0002 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.

Related

commit compared with commands from other repositories

commit next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
commitmarciopuga/cogCommand3772mo agoMITA38Claude Code
standupvvedantb/evaCommand101yesterdayMITA0Claude Code
gitazrtydxb/procoderCommand21111d agoApache-2.0A20Claude Code
session-reportdamusix/atomic-claudeCommand1154d agoMITA31Claude Code
commitechoVic/blade-codeCommand18124d agoMITA8Claude Code
git-workflowHermeticOrmus/LibreUIUX-Claude-CodeCommand1151mo agoMITA14Claude Code
commitjoaquimscosta/arkhe-claude-pluginsCommand2221d agoMITA11Claude Code