What is usage-monitor-commit-push?

A repository workflow for safely staging selected files, committing them, and pushing them to a remote Git repository. Git is the system used to track code changes and share them with other developers.

Use it when the user explicitly asks to commit or push Usage Monitor changes, including the required checks and final status report.

It avoids accidentally committing unrelated files and restores the repository's original author settings after publishing changes.

How edilsonvilarinho/usage-monitor configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to edilsonvilarinho/usage-monitor. 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/edilsonvilarinho/usage-monitor/main/.claude/skills/usage-monitor-commit-push/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/edilsonvilarinho/usage-monitor

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/edilsonvilarinho/usage-monitor/usage-monitor-commit-push/github.svg)](https://agentmods.dev/skills/edilsonvilarinho/usage-monitor/usage-monitor-commit-push)

Your own site

<a href="https://agentmods.dev/skills/edilsonvilarinho/usage-monitor/usage-monitor-commit-push"><img src="https://agentmods.dev/badge/skills/edilsonvilarinho/usage-monitor/usage-monitor-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/skills/edilsonvilarinho/usage-monitor/usage-monitor-commit-push"><img src="https://agentmods.dev/badge/skills/edilsonvilarinho/usage-monitor/usage-monitor-commit-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 597 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.00052	$0.00597
Opus 5.5	$0.00021	$0.00239
Sonnet 5.5	$0.00010	$0.00119
Haiku 4.5	$0.00005	$0.00060

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

Security

Grade A, and why

usage-monitor-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 yesterday.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/commit_and_push.ps1), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/skills/usage-monitor-commit-push/SKILL.md · 55 lines

How it starts

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

Usage Monitor Commit Push

Commit only the intended files, use a temporary agent git identity, and restore the original local git author config before finishing.

Workflow

Read AGENTS.md and README.md first.
Continue only after the user explicitly asks to commit, push, or publish changes.
Inspect repository state with:
- git status --short --branch
- git branch --show-current
- git remote -v
- git diff --stat
- git diff --cached --stat
Stage only explicit file paths. Never use broad staging such as git add . when unrelated changes may exist.
Choose the narrowest relevant verification before the commit:
- Docs-only changes: inspect the diff for coherence.
- Kotlin, UI, history, lifecycle, or repository changes: run gradlew.bat allTests or a narrower relevant test target.
- Installer or packaging changes: run gradlew.bat packageInstaller when the installer behavior is part of the change.
Prefer the bundled script scripts/commit_and_push.ps1 for the actual commit and push.
Report the branch, commit hash, push result, and final git status --short --branch.

Script

Use the bundled PowerShell helper to stage only the requested files, temporarily switch the git identity, restore the previous identity, and optionally skip the push.

Example:

powershell -ExecutionPolicy Bypass -File `
  .claude\skills\usage-monitor-commit-push\scripts\commit_and_push.ps1 `
  -RepoPath C:\Users\edils\workspace\usage-monitor `
  -Message "docs: sync README with current architecture and workflows" `
  -Files README.md `
  -TempUserName claude `
  -TempUserEmail [email protected]

Use -SkipPush when the user asked only for a local commit. Use -DryRun to preview the staging plan without touching the index.

The identity is restored in the script's finally block, so it is restored even when the commit or the push fails.

Guardrails

Do not commit or push without explicit user approval in the current conversation.
Do not stage unrelated changes.
Do not force-push unless the user explicitly asks for it.
Keep commit messages focused on the actual change scope.
Do not modify another agent's uncommitted work in order to make a verification pass. Stop and report instead.

Read the full file on GitHub · 55 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/commit_and_push.ps1 5.5 KB runs code

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.

yesterday Changed · -20 tokens per session a446b61f8352
8d ago First seen · 55 lines · 72 tokens per session scan A 40922e246c94

Subscribe to this mod's changes

usage-monitor-commit-push is a skill published in the GitHub repository edilsonvilarinho/usage-monitor (16 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 597 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-10-16.

Analytics and metrics Claude Code Commits Git and workflow ai anthropic codex compose-desktop

caveman-commit

Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

JuliusBrussee/caveman · 38 tokens

git

Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it…

asgeirtj/system_prompts_leaks · 163 tokens

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens

usage-monitor: Skill for Claude Code