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/kayaerhan/cursor-agent-tr/git_agent_updategit clone --depth 1 https://github.com/KayaErhan/cursor-agent-trWhat 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.00961 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 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 2d 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.
- 2d 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 1mo 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.