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 agentmods add commands/phuctm97/modelfetch/git-pushgit clone --depth 1 https://github.com/phuctm97/modelfetchWhat 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 | $0.00015 | $0.00428 |
| Opus 5 | $0.00008 | $0.00214 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
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 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.
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.
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:
- Format code: Run
pnpm -w formatto format all files - Type check: Run
pnpm exec nx run-many -t typecheckto check TypeScript types - Lint and auto-fix issues: Run
pnpm exec nx run-many -t lint --args=--fixto lint and auto-fix issues - Stage all changes: Run
git add -Ato stage all changes (including any fixes from the above steps) - Review changes: Run
git statusandgit diffto review what will be committed - Create commit: Generate an appropriate commit message based on the changes and create the commit
- 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.
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.
- 2d ago First seen · 26 lines · 15 tokens per session scan A 7c22386e0455
git-push is a command published in the GitHub repository phuctm97/modelfetch (145 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 428 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.