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.
git clone --depth 1 https://github.com/GktuOktay/ai-skillsWrote 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/gktuoktay/ai-skills/git-orchestrator)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/git-orchestrator"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/git-orchestrator/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/rules/gktuoktay/ai-skills/git-orchestrator"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/git-orchestrator.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.00674 |
| Opus 5 | $0.00000 | $0.00337 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
git-orchestrator 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Orchestrator — Git Processes and Repo Manager
You are an orchestrator. Analyze the user's request related to Git, GitHub/GitLab, branch management, committing, PR creation, or repository rules (community standards), and automatically invoke the sub-skills below.
Sub-Skills You Manage
1. git-conventional-commits
When to Invoke:
- When writing a commit message
- When opening a new branch (if a naming convention is required)
- When editing past commits (rebase/squash) to comply with standards
2. git-issue-manager
When to Invoke:
- When opening a new Issue (Bug, Feature Request) on GitHub/GitLab
- When adding a label or milestone to issues
- When creating an issue template
- When performing issue triage/management in an "oh-my-issues" fashion
3. git-pr-reviewer
When to Invoke:
- When opening a Pull Request (PR) (writing the description text)
- When reviewing an incoming PR (code review)
- When deciding on a merge strategy
4. git-repo-setup
When to Invoke:
- When setting up GitHub community standards while starting a new project
- When creating files like
README.md,CONTRIBUTING.md,CODE_OF_CONDUCT.md - When configuring repository settings (branch protection)
5. version-bump
When to Invoke:
- When releasing a new version (SemVer rules)
- When creating a changelog
- When tagging a release
6. change-tracker
When to Invoke:
- When the
CHANGELOG.mdfile needs to be updated according to the "Keep a Changelog" format as code is written - When continuous logging of work done during development into a markdown document (live changelog) is requested
Orchestration Rules
- Analyze: Determine the scope of the request — Just a commit, or the entire PR process?
- Invoke: Read the relevant SKILL.md files and act according to their instructions.
- Consistency: Ensure that generated PR descriptions align with the commit messages (Conventional Commits).
Common Flow Examples
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 · 70 lines · 674 tokens per session scan A 99ec70b79912
git-orchestrator is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 674 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-03.
Other cursor rules, from other repositories
context-dump
Sync 7 days of GitHub activity (commits, PRs, issues, reviews) into a structured context dump.
develop-feature
When the user asks to implement a new feature end-to-end requiring planning, branch creation, implementation, testing, and PR. Use for work that goes beyond a simple fix or ad-hoc task.
new-project-standard
wellmanifest/new-project fail-closed ticket contract for every Cursor session.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
principle
A set of project rules that forbids automatic code submission and the creation of example or demonstration files.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.