agentmods.dev

modelfetch: Command for Claude Code

.claude/commands/git-push.md

git-push is a command for Claude Code from phuctm97/modelfetch. It costs 15 tokens per session (428 once invoked), scanned A, a copy of git-commit, MIT.

A command workflow that formats, checks, lints, commits, and pushes all current changes to a Git remote, the shared repository server. If checks fail, it attempts fixes and repeats the workflow.

In plain words
What is it for?
Use it to format a pnpm workspace, check TypeScript types, lint and fix code, stage and review changes, create a commit, and push the current branch.
Why use it?
It brings the routine pre-commit and push steps into one process, including reviewing what will be staged and creating a descriptive commit message.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is phuctm97/modelfetch's own configuration. It tells Claude Code how to work on modelfetch itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything modelfetch configures →

not rated 145repo 11mo ago A scan 15 tokens copy · 89% MIT archived
View source ↗ phuctm97/modelfetch modelfetch.com
Reuse

Borrowing it

Nothing to install: this file belongs to phuctm97/modelfetch. 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/phuctm97/modelfetch/main/.claude/commands/git-push.md
Clone the repo
git clone --depth 1 https://github.com/phuctm97/modelfetch

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.

agentmods badge for git-push

README.md
[![agentmods](https://agentmods.dev/badge/commands/phuctm97/modelfetch/git-push/github.svg)](https://agentmods.dev/commands/phuctm97/modelfetch/git-push)
Your own site
<a href="https://agentmods.dev/commands/phuctm97/modelfetch/git-push"><img src="https://agentmods.dev/badge/commands/phuctm97/modelfetch/git-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.

agentmods 80×15 button for git-push

Your own site · 80×15
<a href="https://agentmods.dev/commands/phuctm97/modelfetch/git-push"><img src="https://agentmods.dev/badge/commands/phuctm97/modelfetch/git-push.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 428 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 89% copy Near-identical to another mod 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.1 $0.00015 $0.00428
Opus 5.5 $0.00006 $0.00171
Sonnet 5.5 $0.00003 $0.00086
Haiku 4.5 $0.00002 $0.00043

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

Security

Grade A, and why

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

Origin

This is a copy

89% identical to git-commit — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/git-push.md · 26 lines

What it actually says

Run the pre-commit workflow, create a git commit with all changes, and push to the remote repository.

Execute the following steps in order:

  1. Format code: Run pnpm -w format to format all files
  2. Type check: Run pnpm exec nx run-many -t typecheck to check TypeScript types
  3. Lint and auto-fix issues: Run pnpm exec nx run-many -t lint --args=--fix to lint and auto-fix issues
  4. Stage all changes: Run git add -A to stage all changes (including any fixes from the above steps)
  5. Review changes: Run git status and git diff to review what will be committed
  6. Create commit: Generate an appropriate commit message based on the changes and create the commit
  7. Push to remote: Push the current branch to the remote repository with git push

For the commit message:

  • Keep it concise and descriptive
  • Focus on the "why" rather than the "what"
  • DO NOT use conventional commit prefixes (no "fix:", "feat:", "chore:", etc.)

If any of the formatting, type checking, or linting steps fail, attempt to fix the issues. After fixing the issues or making any changes manually, repeat the entire process from step 1 to ensure everything is in order before committing.

If the push fails (e.g., due to remote changes), report the errors to the user for resolution.

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. 2mo ago First seen · 26 lines · 15 tokens per session scan A 7c22386e0455

Subscribe to this mod's changes

git-push is a command published in the GitHub repository phuctm97/modelfetch (145 stars, last pushed 11mo ago), licensed MIT. It adds 15 tokens to every session and 428 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to git-commit, differing in 9 lines, and is treated as a copy.

CommitsGit and workflow
Related

git-push compared with commands from other repositories

git-push next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
git-pushphuctm97/modelfetchCommand14511mo agoMITA15Claude Code
standupvvedantb/evaCommand101yesterdayMITA0Claude Code
gitazrtydxb/procoderCommand211yesterdayApache-2.0A20Claude Code
session-reportdamusix/atomic-claudeCommand1165d agoMITA31Claude Code
commitechoVic/blade-codeCommand18125d agoMITA8Claude Code
git-workflowHermeticOrmus/LibreUIUX-Claude-CodeCommand1151mo agoMITA14Claude Code
commitjoaquimscosta/arkhe-claude-pluginsCommand2223d agoMITA11Claude Code