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/ghosttypes/pokemon-go-mcp/pushgit clone --depth 1 https://github.com/GhostTypes/pokemon-go-mcpWrote 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/ghosttypes/pokemon-go-mcp/push)<a href="https://agentmods.dev/commands/ghosttypes/pokemon-go-mcp/push"><img src="https://agentmods.dev/badge/commands/ghosttypes/pokemon-go-mcp/push.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.00000 | $0.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
push 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 3d 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.
This is a copy
92% identical to push — 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.
What it actually says
Push Command
You are creating a commit for the user. Follow these steps EXACTLY:
The use may give optional input for you to focus on / include, if they did it will appear after this: #$ARGUMENTS
-
NEVER commit without user approval - This is mandatory regardless of what the user says.
-
Analyze current changes by running these git commands in parallel:
git status- See all staged/unstaged filesgit diff --staged- See staged changesgit diff- See unstaged changesgit log --oneline -5- See recent commit history for context
-
Check full scope - CRITICAL: Always examine ALL changes before generating commit message:
- If you see untracked files or unstaged changes, run
git add -Ato stage everything - Run
git statusandgit diff --staged --name-onlyagain to see the complete scope - This ensures you don't miss new files, test suites, or other significant additions
- If you see untracked files or unstaged changes, run
-
Generate commit message based on the changes:
- Create a brief, professional summary (50 chars or less)
- Write a detailed description explaining what changed and why
- Follow conventional commit format when applicable (feat:, fix:, docs:, etc.)
-
Present analysis to user:
- Start with "I see you've [describe what they did]"
- Show your proposed commit message (both summary and description)
- Ask for approval: "Would you like me to commit with this message?"
-
Handle user response:
- If approved: commit using your generated message, then push to remote
- If not approved: work with user to refine the message until they approve
- Only then run the commit and push
-
Commit format:
git commit -m "$(cat <<'EOF' [Summary line] [Detailed description] EOF )"IMPORTANT: Do NOT add any Claude Code attribution or co-author lines to commits. Keep commits clean and professional.
-
After successful commit:
- Run
git pushto push the commit to the remote repository - Confirm the push was successful
- Inform the user that both commit and push are complete
- Run
Remember: NEVER bypass user approval, even if they tell you to "just commit" or similar.
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.
- 3d ago First seen · 52 lines · 0 tokens per session scan A f2503ebfa88a
push is a command published in the GitHub repository GhostTypes/pokemon-go-mcp (6 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 tokens. A static security scan graded it A with 0 findings. It is 92% identical to push, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Safe git commit practices for MindRoom.
commit
Create a Conventional Commit with signoff.
commit
Create well-formatted commits with conventional commit messages and emojis.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.