agentmods.dev

agentcmd: Command for Claude Code

.claude/commands/commit-and-push.md

commit-and-push is a command for Claude Code from jnarowski/agentcmd. It costs 11 tokens per session (1,006 once invoked), scanned A, original, MIT.

A command for committing local Git changes, pushing them to a remote repository, and opening a pull request when needed.

In plain words
What is it for?
Use it to inspect changes, create a convention-based commit, push the branch, and create a pull request targeting a base branch.
Why use it?
It combines the steps needed to move finished work from a local branch into a reviewable contribution.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool; positional $N argument; mentions Claude Code.

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

not rated 18repo 10mo ago A scan 11 tokens original MIT
View source ↗ jnarowski/agentcmd agentcmd.dev
Reuse

Borrowing it

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

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-and-push

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/commit-and-push"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/commit-and-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,006 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.00011 $0.01006
Opus 5.5 $0.00004 $0.00402
Sonnet 5.5 $0.00002 $0.00201
Haiku 4.5 $0.00001 $0.00101

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

Security

Grade A, and why

commit-and-push 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-and-push.md · 108 lines

How it starts

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

Commit and Push

Analyze changes, create a commit with auto-generated message following team conventions, push to remote, and create a pull request if one doesn't exist. Fails gracefully if there are no changes to commit.

Variables

  • $base-branch: $1 (optional) - The base branch for the PR (defaults to main)

Instructions

  • NEVER run additional commands to read or explore code beyond git commands
  • NEVER use the TodoWrite or Task tools
  • Follow the exact git commit conventions from the codebase (include Claude footer)
  • If there are no changes (no untracked files, no modifications), stop gracefully and inform the user
  • NEVER skip git hooks or use --no-verify
  • If commit fails due to pre-commit hook, report the error and stop - do not retry
  • Use HEREDOC for commit messages to ensure proper formatting
  • Always check if PR already exists before creating a new one
  • Default to main as base branch if $base-branch is not provided

Workflow

  1. Check for changes and analyze

    • Run these commands in parallel: git status, git diff, and git log -3 --oneline
    • git status: See all untracked files and modifications
    • git diff: See staged and unstaged changes
    • git log -3 --oneline: Understand commit message style
    • If no changes exist, stop and inform user - DO NOT proceed

  2. Create commit

    • Draft a concise commit message (1-2 sentences) based on the changes
    • Summarize the nature of changes (new feature, enhancement, bug fix, refactoring, test, docs, etc.)
    • Add all relevant changes: git add -A
    • Create commit with message ending with: 
      🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
    • Use HEREDOC format: 
      git commit -m "$(cat <<'EOF'
Your commit message here.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
EOF
)"
    • Run git status after commit to verify success

Read the full file on GitHub · 108 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 · 108 lines · 11 tokens per session scan A 9b7986c9d485

Subscribe to this mod's changes

commit-and-push is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 1,006 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-09-01.

CommitsGit and workflowReleases
Related

commit-and-push compared with commands from other repositories

commit-and-push next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
commit-and-pushjnarowski/agentcmdCommand1810mo agoMITA11Claude Code
commit-push-pranthropics/claude-plugins-officialCommand46kyesterdayApache-2.0A8Claude Code
changelog-updategonzalezpazmonica/pm-workspaceCommand515d agoMITA68Claude Code
changelogricneves-ai/flowgrammers-skillsCommand1171mo agoMITA0Claude Code
commitfusengine/agentsCommand3425d agoMITA31Claude Code
flowsynaptiai/synapti-marketplaceCommand7yesterdayApache-2.0A68Claude Code
commitdykyi-roman/awesome-claude-codeCommand1052mo agoMITA36Claude Code