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/wangke19/gemini-ai-helpers/summarygit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/summary)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/summary"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/summary.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.00602 |
| Opus 5 | $0.00006 | $0.00301 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
summary 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 yesterday.
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
94% identical to summary — 2 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
git:summary
Synopsis
/git:summary
Description
The git:summary command provides a comprehensive overview of the current Git repository state. It displays the current branch, tracking status, working tree status, and recent commit history in a single concise view. This command is designed to give developers quick context about their repository without running multiple Git commands manually.
It provides essential information for developers including:
- Current branch and remote tracking status (ahead/behind)
- Working tree status (modified, staged, and untracked files)
- Recent commit history with one-line summaries
- Uncommitted changes summary
The spec sections is inspired by https://man7.org/linux/man-pages/man7/man-pages.7.html#top_of_page
Implementation
- Executes multiple git commands to gather repository state
- Retrieves current branch name and tracking information
- Shows git status for modified, staged, and untracked files
- Displays last 5 commits with one-line summaries
- Summarizes uncommitted changes
- Formats output for clear readability
- All information is read-only with no side effects
Implementation logic:
# Get current branch and tracking status
git branch -vv
# Show working tree status
git status --short
# Display recent commits
git log --oneline -5
# Summarize uncommitted changes
git diff --stat
Return Value
- Gemini agent text: Formatted summary including:
- Current branch name and remote tracking status
- List of modified, staged, and untracked files
- Last 5 commit messages with hashes
- Statistics of uncommitted changes
Examples
- Basic usage:
Output:/git:summaryCurrent branch: main Your branch is up to date with 'origin/main'. Modified files: M src/index.ts ?? temp/ Recent commits: abc123 Fix authentication bug def456 Add user profile feature ghi789 Update dependencies jkl012 Refactor database layer mno345 Initial commit Uncommitted changes: 1 file changed, 15 insertions(+), 3 deletions(-)
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.
- yesterday First seen · 103 lines · 13 tokens per session scan A ceeb87669ef2
summary is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 602 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to summary, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
spec-kitty.implement
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
release-prod
Guide you through promoting stage → production.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
mem-search
Full-text search in the memory vault (archives, contexts, histories, index).