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/pranav-karra-3301/tuck/gitgit clone --depth 1 https://github.com/Pranav-Karra-3301/tuckWrote 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/commands/pranav-karra-3301/tuck/git)<a href="https://agentmods.dev/commands/pranav-karra-3301/tuck/git"><img src="https://agentmods.dev/badge/commands/pranav-karra-3301/tuck/git.svg" alt="Measured on agentmods" 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 | $0.00003 | $0.00286 |
| Opus 5 | $0.00002 | $0.00143 |
| Sonnet 5 | $0.00001 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
git 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 4d 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
Sync Main
Fetch and pull latest from main branch.
git checkout main && git fetch origin && git pull origin main
New Feature
Create a new feature branch.
git checkout -b feat/FEATURE_NAME
Replace FEATURE_NAME with your feature name.
New Fix
Create a new bugfix branch.
git checkout -b fix/FIX_NAME
Replace FIX_NAME with the bug description.
Commit Feature
Create a feature commit (triggers minor version bump).
git add -A && git commit -m "feat: DESCRIPTION"
Commit Fix
Create a fix commit (triggers patch version bump).
git add -A && git commit -m "fix: DESCRIPTION"
Commit Docs
Create a documentation commit (no version bump).
git add -A && git commit -m "docs: DESCRIPTION"
Commit Refactor
Create a refactor commit (no version bump).
git add -A && git commit -m "refactor: DESCRIPTION"
Status
Check git status and recent commits.
git status && git log --oneline -5
Push Branch
Push current branch to origin.
git push -u origin HEAD
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.
- 4d ago First seen · 80 lines · 3 tokens per session scan A ed09d449764f
git is a command published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 1mo ago), licensed MIT. It adds 3 tokens to every session and 286 once invoked, about $0.0000 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.
Other commands, from other repositories
commit
Split working changes into multiple logical git commits.
commit
Create well-formatted commits with conventional commit messages and emoji.
commit-and-create-mr
Commit and create MR on Gitlab.
logical-commits
Command "logical-commits" from sumihiro3/Monomi, covering logical commits command, 処理の流れ, コミットの分類基準, 機能追加 (feat:) and リファクタリング (refactor:).
review
Recent git commits: !git log --oneline -10.
push-commit
Create a new commit from the current repo changes and push it.