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.
git clone --depth 1 https://github.com/heyAyushh/staccnpx agentmods add commands/heyayushh/stacc/commit-push-prWrote 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.
[](https://agentmods.dev/commands/heyayushh/stacc/commit-push-pr)<a href="https://agentmods.dev/commands/heyayushh/stacc/commit-push-pr"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/commit-push-pr/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.
<a href="https://agentmods.dev/commands/heyayushh/stacc/commit-push-pr"><img src="https://agentmods.dev/badge/commands/heyayushh/stacc/commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01490 |
| Opus 5.5 | $0.00000 | $0.00596 |
| Sonnet 5.5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
commit-push-pr 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit, push & create PR (one-shot)
Overview
This command is a template for committing changes on the current branch, pushing them to the remote,
and then creating a Pull Request.
Branch protection (e.g. disallowing direct pushes to main/master), quality checks (lint / test / build),
and the PR creation flow (AI/MCP vs CLI) should be customized per project.
Preconditions
- There are modified files.
- The remote
originis configured. - GitHub CLI (
gh) is installed (for the CLI fallback). - You are on a working branch (e.g.
feature/...,fix/...).
Steps (non-interactive)
- Check the branch (prevent direct pushes to main/master).
- Optionally run quality checks (lint / test / build).
- Stage changes (
git add -A). - Commit (use an environment variable or argument for the message).
- Push (
git push -u origin <current-branch>). - Create a PR (via MCP or CLI, depending on your environment).
Usage
A) Minimal input (recommended)
You only specify the commit message; PR title/body are generated by AI (MCP, etc.).
# Commit message only (example)
MSG="fix: remove unnecessary debug log output"
# One-shot execution
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"
# At this point, ask AI to create a PR, for example:
# - Infer intent from the branch name
# - Inspect changes via: git diff --name-status
# - Generate PR title and body
# - Create the PR via mcp_github_create_pull_request or `gh pr create`
Note: MCP (Model Context Protocol) is a standard protocol for safely allowing agents to interact with external services like GitHub.
To use it for PR creation, you will need an MCP-compatible environment and GitHub integration. See: https://modelcontextprotocol.io/
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.
- 25d ago Changed e8113f44d740
- 1mo ago First seen · 197 lines · 0 tokens per session scan A a4d9daa4f0f8
commit-push-pr 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 1,490 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.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Context-aware Git commit assistant with smart pre-commit checks.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.