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 rules/yukimiyatake/costgate/git-feature-branchgit clone --depth 1 https://github.com/YukiMiyatake/costgateWrote 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/rules/yukimiyatake/costgate/git-feature-branch)<a href="https://agentmods.dev/rules/yukimiyatake/costgate/git-feature-branch"><img src="https://agentmods.dev/badge/rules/yukimiyatake/costgate/git-feature-branch.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.00404 | $0.00404 |
| Opus 5 | $0.00202 | $0.00202 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
git-feature-branch 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.
What it actually says
Git ブランチ運用（CostGate）
必須（エージェント向け）
コミット・push・PR は npm run feat:ship を使う。 Cursor / ローカルは PR 作成まで。CI・レビューコメント・auto-merge は GitHub Actions（ci.yml + pr-automation.yml）が担当。
git add <files>
npm run feat:ship -- --message "日本語のコミットメッセージ"
# マージ待ち + local main 同期（任意）
npm run feat:ship -- -m "…" --wait
# 手動レビュー
npm run feat:ship -- -m "…" --draft
# マージ後に main 同期
npm run feat:sync
mainへの直接 push 禁止（.githooks/pre-push）- コミットメッセージは日本語
- 1 機能 = 1 ブランチ = 1 PR（
main向け） developブランチは使わない
ブランチ開始のみ
npm run feat:start -- short-name
初回セットアップ
npm run hooks:install
リリース
バージョンは repo にコミットしてから tag push。詳細: docs/RELEASE.md
npm run release:version -- 0.6.0 --note "変更概要"
npm run feat:ship -- -m "chore: release v0.6.0"
# マージ後
git tag v0.6.0 && git push origin v0.6.0
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 · 51 lines · 404 tokens per session scan A 4350b97cf6b8
git-feature-branch is a cursor rule published in the GitHub repository YukiMiyatake/costgate (0 stars, last pushed 1mo ago), licensed MIT. It adds 404 tokens to every session, about $0.0020 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.