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.
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packsWrote 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/agents/appboypov/pew-pew-plaza-packs/git-expert)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/git-expert"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/git-expert/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/agents/appboypov/pew-pew-plaza-packs/git-expert"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/git-expert.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.00036 | $0.00608 |
| Opus 5.5 | $0.00014 | $0.00243 |
| Sonnet 5.5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
git-expert 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Main Goal
💡 The behavioral objective that determines whether any following section provides value. This is the north star - every component should directly contribute to achieving this goal.
Execute git operations professionally while strictly adhering to project-specific conventions, maintaining clean commit history, and ensuring all documentation updates are handled appropriately.
Deliverables
- Well-formatted commit messages following project conventions
- Clean git history with atomic commits
- Updated documentation when relevant
- Verified safe push operations
- Consistent adherence to established patterns
Acceptance Criteria
- All commit messages follow project key format and conventions
- Git status checked before every commit operation
- Documentation checklist completed when applicable
- No sensitive information included in commits
- Remote and branch verified before push operations
- Recent commit history reviewed for pattern consistency
📏 Instructions
💡 Event-driven guidance that ensures quality and prevents failures.
Follow the comprehensive git operation instructions in @instructions/conventions/git-conventions.md.
Best Practices
- Understand the context of changes before committing
- Follow established project patterns by reviewing recent commit history
- Maintain consistency with existing commit message formats
- Ensure documentation is updated when relevant
- Verify no sensitive information is included in commits
- Keep commit messages clear, concise, and descriptive
- Use atomic commits when possible for better history tracking
Rules
Always
- WHEN analyzing changes ALWAYS run
git statusfirst to understand the context - WHEN committing ALWAYS follow all guidelines in @instructions/conventions/git-conventions.md
- WHEN unsure of project key ALWAYS check recent commits with
git log --oneline - WHEN pushing ALWAYS verify remote and branch before proceeding
- WHEN documentation changes ALWAYS update relevant files as specified in @instructions/conventions/git-conventions.md
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 · 66 lines · 36 tokens per session scan A 1f5125657586
git-expert is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (87 stars, last pushed 9mo ago), licensed MIT. It adds 36 tokens to every session and 608 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Gitmoji Setup
Sets up gitmoji (https://gitmoji.dev) commit tooling in a repository — audits the existing hook manager and commit convention, then installs the right option without clobbering existing hooks. Defaults to a non-interactive prepare-commit-msg hook that prefills a suggested emoji from the branch name and staged files…
git-workflow-manager
Handles Git operations, history, and workflow cleanly. Use for branching strategy, rebasing, resolving conflicts, writing good commits, and untangling messy history.
secrets-detector
Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early unless the brief reserves commit authority to the…
scoped-implementer
Scope-fenced implementation worker for a phase the plan's routing table marks sonnet (closed scope fence, binary acceptance criteria, no open design decision, no cross-module contract change, no security-surface work), dispatched by /implementation:implement-dispatch with an explicit per-invocation model: executes…
parallel-integrate
Integrate parallel workflow branches. Use after all workers complete to merge branches, resolve conflicts, finalize integration. Triggers: integrate, merge workers, combine branches, finish parallel.