A command template that stages changed files, creates a Git commit on the current branch, and pushes it to the remote repository. Git is a tool for tracking code changes, while a remote repository is the shared copy hosted elsewhere.

Use it to save local changes with a commit message and send them to the configured remote repository, subject to the project's branch rules.

It removes the need to repeat the commit-and-push commands manually and can guard against direct pushes to the main branches. Project-specific checks such as linting, tests, or builds can be added.

commit-push — Command for Claude Code and Cursor by heyAyushh/stacc

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/heyAyushh/stacc

agentmods

npx agentmods add commands/heyayushh/stacc/commit-push

Made for: Claude Code, Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/heyayushh/stacc/commit-push/github.svg)](https://agentmods.dev/commands/heyayushh/stacc/commit-push)

Your own site

<a href="https://agentmods.dev/commands/heyayushh/stacc/commit-push"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/commit-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/heyayushh/stacc/commit-push"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/commit-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 647 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00647
Opus 5.5	$0.00000	$0.00259
Sonnet 5.5	$0.00000	$0.00129
Haiku 4.5	$0.00000	$0.00065

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

Security

Grade A, and why

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

.cursor/commands/commit-push.md · 85 lines

How it starts

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

Commit & push (current branch)

Overview

This is a generic command template for committing changes on the current branch and pushing them to the remote.
Branch policies (such as disallowing direct pushes to main/master) and pre-commit quality checks (lint / test / build, etc.) should be adjusted per project.

Preconditions

There are modified files.
The remote origin is configured.

Steps (non-interactive)

Check the current branch and prevent direct pushes to main/master.
Optionally run quality checks (lint / test / build, etc.).
Stage changes (git add -A).
Commit (using an environment variable or argument for the message).
Push (git push -u origin <current-branch>).

Usage

A) Safe one-liner execution (with message argument)

MSG="<Prefix>: <summary (imperative / concise)>" \
BRANCH=$(git branch --show-current) && \
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then \
  echo "⚠️ Direct pushes to main/master are not allowed"; exit 1; \
fi

# Optional quality checks (only if needed)
# Example:
# ./scripts/lint.sh && ./scripts/test.sh && ./scripts/build.sh || exit 1

git add -A && \
git commit -m "$MSG" && \
git push -u origin "$BRANCH"

Example:

MSG="fix: remove unnecessary debug log output" \
BRANCH=$(git branch --show-current) && \
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then \
  echo "⚠️ Direct pushes to main/master are not allowed"; exit 1; \
fi

# Optional quality checks (only if needed)
# ./scripts/quality-check.sh || exit 1

git add -A && git commit -m "$MSG" && git push -u origin "$BRANCH"

B) Step-by-step execution (readability first)

# 1) Check branch
BRANCH=$(git branch --show-current)
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
  echo "⚠️ Direct pushes to main/master are not allowed"; exit 1;
fi

# 2) Optional local quality checks (add as needed)
# Example:
# echo "Running quality checks..."
# ./scripts/lint.sh && ./scripts/test.sh && ./scripts/build.sh || exit 1

# 3) Stage changes
git add -A

# 4) Commit (edit the message)
git commit -m "<Prefix>: <summary (imperative / concise)>"

# 5) Push
git push -u origin "$BRANCH"

Read the full file on GitHub · 85 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.

1mo ago First seen · 85 lines · 0 tokens per session scan A b0198cef1a5c

Subscribe to this mod's changes

commit-push is a command published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 647 tokens. 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.

Commits Git and workflow

commit-push