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 skills/baphuongna/pi-crew/git-masternpx skills add baphuongna/pi-crew --skill git-mastergit clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/git-master)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/git-master"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/git-master.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.00013 | $0.01746 |
| Opus 5 | $0.00006 | $0.00873 |
| Sonnet 5 | $0.00003 | $0.00349 |
| Haiku 4.5 | $0.00001 | $0.00175 |
Grade A, and why
git-master 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.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-master
Use this skill for commit/release hygiene. This skill covers git workflow from local changes to published releases.
Pre-commit Checklist
Before every commit:
- Run
git status --short— understand what changed - Stage only files related to the current task
- Review staged diff with
git diff --staged - Check for unintended changes (generated files, temp files, secrets)
- Ensure tests pass locally before committing
Commit Rules
- Independent commits: Each commit should be self-contained and revertible. Don't mix unrelated changes.
- Concise messages: Use imperative mood, 50 chars or less for subject. Add body for context.
- Format:
type(scope): subjectwhere type isfix,feat,chore,docs,test,refactor - Do not include: secrets, OTPs, local temp files,
node_modules,dist/,*.log,*.tmp - Do not push/publish unless explicitly requested
- Verify before staging large generated files (tarballs, build outputs)
Commit Message Format
type(scope): short description (50 chars max)
Longer description if needed. Explain WHY the change was made,
not just what changed. Reference issues/PRs if applicable.
Refs: #123
Examples:
fix(live-agent): prevent cross-workspace agent access
feat(widget): add snapshot cache with 500ms TTL
docs(skills): add event-log-tracing skill
chore(tests): add integration test for reconcileAllStaleRuns
Branch Naming
| Pattern | Use case | Example |
|---|---|---|
fix/<description> |
Bug fixes | fix/ghost-run-display |
feat/<description> |
New features | feat/skill-templates |
docs/<description> |
Documentation | docs/skills-deep-research |
chore/<description> |
Tooling, CI | chore/update-ci-node22 |
hotfix/<description> |
Urgent production fixes | hotfix/secret-leak |
Rollback Procedures
Revert last commit (safe, keeps history)
git revert HEAD
git push
Reset to known-good state (rewrites history)
# Soft: keep changes staged
git reset --soft HEAD~1
# Mixed: keep changes unstaged
git reset HEAD~1
# Hard: discard all changes (DESTRUCTIVE)
git reset --hard <commit-hash>
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 · 240 lines · 13 tokens per session scan A 31ae0c5fb3a8
git-master is a skill published in the GitHub repository baphuongna/pi-crew (50 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 1,746 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…