Borrowing it
Nothing to install: this file belongs to KayaErhan/cursor-agent-tr. 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/KayaErhan/cursor-agent-tr/main/.cursor/commands/git_agent_update.mdgit clone --depth 1 https://github.com/KayaErhan/cursor-agent-trWrote 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/kayaerhan/cursor-agent-tr/git_agent_update)<a href="https://agentmods.dev/commands/kayaerhan/cursor-agent-tr/git_agent_update"><img src="https://agentmods.dev/badge/commands/kayaerhan/cursor-agent-tr/git_agent_update/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/kayaerhan/cursor-agent-tr/git_agent_update"><img src="https://agentmods.dev/badge/commands/kayaerhan/cursor-agent-tr/git_agent_update.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.00961 |
| Opus 5.5 | $0.00000 | $0.00384 |
| Sonnet 5.5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
git_agent_update 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/git_agent_update - Agent Komutlarini Guncelle
Bu komut, ajanin komut/rule setini git reposundan guncelleyip mevcut ortama senkronlar.
Amac
- Uzak repoda yeni surum var mi kontrol et
- Varsa repoyu guncelle (
git pull) - Yeni veya degisen
.cursor/commands,.cursor/rulesve.cursor/agentsdosyalarini tespit et - Bu dosyalar varsa kullaniciya sormadan global kopyalama yapma; asagidaki soruyu kullan
Is Akisi
- Git repo kontrolu:
git statusile yerel degisiklikleri kontrol et.- Yerel degisiklik varsa once raporla; otomatik overwrite yapma.
- Pull oncesi referans:
git rev-parse HEADile mevcut commit hash’ini not al (ONCEKI_COMMIT).
- Uzak kontrol:
git fetch origin- Local ile remote commit farkini kontrol et.
- Guncelleme:
- Guncelleme varsa
git pull --ff-onlyuygula. - Fast-forward mumkun degilse sebebi raporla.
- Guncelleme varsa
- Degisen dosya tespiti (pull basarili ve commit ilerlediyse):
git diff --name-only ONCEKI_COMMIT..HEAD -- .cursor/commands .cursor/rules .cursor/agentsile listele.- Veya
git log -1 --name-only/git show --name-only --pretty="" HEADile son commit’te bu yollarda degisen dosyalari al. - Bos degilse: asagidaki kullanici onayi adimina gec.
- Kullanici onayi (yeni veya guncellenen komut/rule varsa — zorunlu):
-
Otomatik olarak
~/.cursor/commandsveya~/.cursor/rulesaltina kopyalama yapma. -
Kullaniciya acikca su anlamda sor (metin serbest ama soru sart):
"Yeni veya guncellenen komut, kural veya agent dosyalari var. Bunlari global Cursor klasorune (
~/.cursor/commands,~/.cursor/rules,~/.cursor/agents) eklemek veya mevcut dosyalari bu surumle degistirmek istiyor musunuz?" -
Kullanici evet derse:
- Windows:
$env:USERPROFILE\.cursor\commands,$env:USERPROFILE\.cursor\rules,$env:USERPROFILE\.cursor\agents - macOS/Linux:
~/.cursor/commands,~/.cursor/rules,~/.cursor/agents - Eksik klasorleri olustur; ilgili dosyalari repodan kopyala.
- Windows:
-
Kullanici hayir veya netleştirme istemezse: sadece repodaki dosyalarin listesini ve yolunu raporla; global kopyalama yapma.
-
- Proje bazli kullanim:
- Repodaki
.cursor/commands,.cursor/rules,.cursor/agentsproje acikken aktif olur.
- Repodaki
- Dogrulama:
- Yeni veya guncellenen komut dosyalarini isim bazinda listele.
/menusunda gorunmesi gereken komutlari raporla.
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 · 70 lines · 0 tokens per session scan A 8ec0e769dce1
git_agent_update is a command published in the GitHub repository KayaErhan/cursor-agent-tr (6 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 961 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-08-31.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.