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.
npx skills add CommonstackAI/ClawBox --skill clawbox-git-commit-pushgit clone --depth 1 https://github.com/CommonstackAI/ClawBoxWrote 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/skills/commonstackai/clawbox/clawbox-git-commit-push)<a href="https://agentmods.dev/skills/commonstackai/clawbox/clawbox-git-commit-push"><img src="https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-git-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.
<a href="https://agentmods.dev/skills/commonstackai/clawbox/clawbox-git-commit-push"><img src="https://agentmods.dev/badge/skills/commonstackai/clawbox/clawbox-git-commit-push.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.00047 | $0.00381 |
| Opus 5.5 | $0.00019 | $0.00152 |
| Sonnet 5.5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
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 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.
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 --branchgit diff --statgit diff --cached --stat- Targeted
git diff -- <paths>for files intended for the commit
Workflow
- Inspect repo state before staging anything.
- Confirm the requested commit scope from actual modified files, not assumptions.
- Stage only intended paths with
git add <paths>. - Create the commit with
git commit -m "...". - Check upstream with
git rev-parse --abbrev-ref --symbolic-full-name @{u}. - Use
git pushwhen upstream exists, orgit push -u origin <branch>when the target is obvious. - 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 --branchbefore and after the commit. - Run
git log --oneline -1after the commit. - If pushed, verify the branch is no longer ahead with
git status --short --branch.
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.
- 2mo ago First seen · 40 lines · 47 tokens per session scan A 9172e4eea083
clawbox-git-commit-push is a skill published in the GitHub repository CommonstackAI/ClawBox (22 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 381 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.
Other skills, from other repositories
github
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
commit-message
Generate a clean, conventional commit message from a description of your changes.
paseo-alignfirst-workspace
Register or archive an AlignFirst workspace or an existing worktree as a Paseo workspace. Read it before creating or removing any workspace or worktree when the session runs inside Paseo.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.