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 skills add GktuOktay/ai-skills --skill git-orchestratorgit 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/skills/gktuoktay/ai-skills/git-orchestrator)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/git-orchestrator"><img src="https://agentmods.dev/badge/skills/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/skills/gktuoktay/ai-skills/git-orchestrator"><img src="https://agentmods.dev/badge/skills/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.00053 | $0.00678 |
| Opus 5.5 | $0.00021 | $0.00271 |
| Sonnet 5.5 | $0.00011 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
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 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 — 72 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.
- 1mo ago First seen · 72 lines · 53 tokens per session scan A e28a5e60e7cd
git-orchestrator is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 678 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit.…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
dev-commit
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or finish work with a conventional commit while avoiding unrelated user changes.
pr-workflow
Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining. Use when user wants to commit changes, get a second-opinion code review from Codex, push changes, create a PR, check PR status, fix review comments, clean up branches after merge, or mine tribal knowledge from PR reviews.…