Borrowing it
Nothing to install: this file belongs to rinerebox1/deno-gemini-grounding-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rinerebox1/deno-gemini-grounding-mcp-server/main/.gemini/commands/commit-and-pr.mdgit clone --depth 1 https://github.com/rinerebox1/deno-gemini-grounding-mcp-serverWrote 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/rinerebox1/deno-gemini-grounding-mcp-server/commit-and-pr)<a href="https://agentmods.dev/commands/rinerebox1/deno-gemini-grounding-mcp-server/commit-and-pr"><img src="https://agentmods.dev/badge/commands/rinerebox1/deno-gemini-grounding-mcp-server/commit-and-pr/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/commands/rinerebox1/deno-gemini-grounding-mcp-server/commit-and-pr"><img src="https://agentmods.dev/badge/commands/rinerebox1/deno-gemini-grounding-mcp-server/commit-and-pr.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.00000 | $0.01077 |
| Opus 5 | $0.00000 | $0.00539 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
commit-and-pr 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 8d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
変更のコミットとPR作成
現在の変更をコミットし、適切なブランチを作成してプルリクエストを作成します。GEMINI.mdの「GitHub操作」セクションの規約に従います。
実行手順
1. 変更内容の確認
git status # 変更ファイルの確認
git diff # 変更内容の確認
git log --oneline -10 # 最近のコミット履歴を確認
2. コミットメッセージの作成
GEMINI.mdで定義されているフォーマットに従います：
<変更の種類>: <変更内容の要約>
詳細な説明（必要に応じて）
🤖 Generated with [Gemini CLI](https://ai.google.dev/gemini-api/docs/cli)
Co-Authored-By: Gemini <[email protected]>
3. ブランチ名の命名規則
変更の種類に応じて適切なプレフィックスを使用：
feature/- 機能追加fix/- バグ修正refactor/- リファクタリングdocs/- ドキュメント更新test/- テスト追加・修正
4. ラベルの命名規則
PRに付けるラベル：
enhancement- 機能追加bug- バグ修正refactor- リファクタリングdocumentation- ドキュメントtest- テスト
5. 実行ステップ
-
変更内容の分析
- git statusとgit diffで変更を確認
- 変更の種類を判断（feature/fix/refactor/docs/test）
-
ブランチの作成
git checkout -b <branch-type>/<descriptive-name> -
ステージングとコミット
git add <files> git commit -m "$(cat <<'EOF' <type>: <summary> <detailed description if needed> 🤖 Generated with [Gemini CLI](https://ai.google.dev/gemini-api/docs/cli) Co-Authored-By: Gemini <[email protected]> EOF )" -
リモートへのプッシュ
git push -u origin <branch-name> -
PRの作成
make pr TITLE="<PR title>" BODY="<PR description>" LABEL="<label>" # または gh pr create --title "<title>" --body "$(cat <<'EOF' ## Summary - <変更点1> - <変更点2> ## Test plan - [ ] make check-allが成功することを確認 - [ ] 関連するテストが追加されていることを確認 - [ ] ドキュメントが更新されていることを確認 🤖 Generated with [Gemini CLI](https://ai.google.dev/gemini-api/docs/cli) EOF )"
注意事項
-
コミット前の確認
make check-allが成功することを確認- 不要なファイルが含まれていないことを確認
- センシティブな情報が含まれていないことを確認
-
コミットメッセージ
- 変更内容を明確に記述
- なぜ変更したかを説明（whatよりwhy）
- 日本語での記述も可
-
PR作成時
- テストプランを必ず含める
- レビュアーが理解しやすい説明を心がける
- 関連するIssueがあればリンクする
使用例
# 機能追加のPR
make pr TITLE="feat: ユーザー認証機能を追加" BODY="JWTトークンベースの認証システムを実装しました" LABEL="enhancement"
# バグ修正のPR
make pr TITLE="fix: ログイン時の500エラーを修正" BODY="認証トークンの検証ロジックを修正しました" LABEL="bug"
# ドキュメント更新のPR
make pr TITLE="docs: APIドキュメントを更新" BODY="新しいエンドポイントの説明を追加しました" LABEL="documentation"
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.
- 8d ago First seen · 123 lines · 0 tokens per session scan A bb829cfc7afa
commit-and-pr is a command published in the GitHub repository rinerebox1/deno-gemini-grounding-mcp-server (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,077 tokens. 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-09-01.
Other commands, from other repositories
review-diff
Review the current working diff for correctness, security, and reuse.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
fix-comments
Address PR review comments by implementing requested changes automatically.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.