clawbox-git-commit-push

A workflow guide for safely staging, committing, and pushing ClawBox repository changes with Git. Git is a version-control system that records changes to code and sends them to a shared remote repository.

In plain words
What is it for?
Checking repository status, selecting intended files, creating a non-interactive commit, verifying the branch destination, and pushing it.
Why use it?
It reduces the risk of mixing unrelated files into a commit or using unsafe Git operations.

Skill for Claude CodeCodex

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 skills/commonstackai/clawbox/clawbox-git-commit-push
Any agent
npx skills add CommonstackAI/ClawBox --skill clawbox-git-commit-push
Clone the repo
git clone --depth 1 https://github.com/CommonstackAI/ClawBox

Made for: Claude Code, Codex.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 381 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.00047 $0.00381
Opus 5 $0.00023 $0.00191
Sonnet 5 $0.00009 $0.00076
Haiku 4.5 $0.00005 $0.00038

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

Security

Grade A, and why

clawbox-git-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 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.

.agents/skills/clawbox-git-commit-push/SKILL.md · 40 lines

What it actually says

ClawBox Git Commit Push

Use this skill when the task is to prepare a clean git commit and push it from the current ClawBox repository.

Read first

  • git status --short --branch
  • git diff --stat
  • git diff --cached --stat
  • Targeted git diff -- <paths> for files intended for the commit

Workflow

  1. Inspect repo state before staging anything.
  2. Confirm the requested commit scope from actual modified files, not assumptions.
  3. Stage only intended paths with git add <paths>.
  4. Create the commit with git commit -m "...".
  5. Check upstream with git rev-parse --abbrev-ref --symbolic-full-name @{u}.
  6. Use git push when upstream exists, or git push -u origin <branch> when the target is obvious.
  7. Report the commit hash, branch, and push result.

Guardrails

  • Never use destructive commands such as git reset --hard, git checkout --, rebase, or force-push unless the user explicitly asks.
  • Never stage unrelated or generated files silently.
  • Never amend a commit unless explicitly requested.
  • Prefer non-interactive git commands only.
  • Stop and ask when branch target, commit scope, or staged changes are ambiguous.

Verification

  • Run git status --short --branch before and after the commit.
  • Run git log --oneline -1 after the commit.
  • If pushed, verify the branch is no longer ahead with git status --short --branch.
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 · 40 lines · 47 tokens per session scan A 9172e4eea083

Subscribe to this mod's changes

clawbox-git-commit-push is a skill published in the GitHub repository CommonstackAI/ClawBox (22 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 381 once invoked, about $0.0002 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.