Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dineshdb/pienpx agentmods add skills/dineshdb/pie/gitWrote 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/dineshdb/pie/git)<a href="https://agentmods.dev/skills/dineshdb/pie/git"><img src="https://agentmods.dev/badge/skills/dineshdb/pie/git/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/dineshdb/pie/git"><img src="https://agentmods.dev/badge/skills/dineshdb/pie/git.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.00011 | $0.00372 |
| Opus 5.5 | $0.00004 | $0.00149 |
| Sonnet 5.5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
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 1mo 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
Advanced Git Operations
Treat history as a document to be groomed for clarity.
1. History Surgery
git rebase -i HEAD~n # Groom last n commits (squash/edit/drop)
git commit --amend --no-edit # Add staged changes to last commit
git cherry-pick <hash> # Apply specific commit to current branch
2. Recovery & Undo
git reflog # Find "lost" commits (HEAD history)
git reset --hard HEAD@{n} # Restore to a specific reflog state
git reset --soft HEAD~1 # Undo commit, keep changes staged
git restore <file> # Discard local changes
3. Diagnostics & Trace
git log -S "string" # Find when a string was added/removed (Pickaxe)
git log -L :<func>:<file> # Evolution of a specific function
git blame -L 10,20 <file> # Line-level authorship
git show --name-only <hash> # List files changed in a commit
4. Maintenance
git stash push -m "msg" # Save dirty state
git stash pop # Restore dirty state
git clean -fd # Remove untracked files/dirs
git worktree add ../path br # Work on another branch simultaneously
Principles
- Atomic Commits: One logical change per commit.
- Linear History: Prefer rebase over merge for feature updates.
- Descriptive Messages: Focus on "why" more than "what".
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.
- 1mo ago First seen · 45 lines · 11 tokens per session scan A 9cee9e2ed389
git is a skill published in the GitHub repository dineshdb/pie (2 stars, last pushed 28d ago), licensed MIT. It adds 11 tokens to every session and 372 once invoked, about $0.0000 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-31.
Other skills, from other repositories
github-pr-rebase-merge
Merge a stack of GitHub PRs sequentially when they share files and will cause cascading conflicts. Triggers when user says "merge the PRs sorban" or similar, and the PRs come from external forks (cannot push back to PR branch).
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
release
Create a new versioned release with changelog. Bumps version in code, updates CHANGELOG.md, commits, tags, and pushes using the repository release flow. GitHub Actions creates the release and uses only the current changelog section as release notes. Use when the user says "release", "cut a release", "bump version"…
publish-release
Publish a new nudge release end-to-end — version bump PR, v-tag, GitHub release with notes, and the CI pipeline that builds binaries/APK and updates Homebrew + AUR. Use when asked to release, publish, ship, or tag a new version. Encodes the exact merge-gate and notes-before-artifacts ordering, so no step needs…
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.