Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mimukit/skillsnpx agentmods add skills/mimukit/skills/gitkitWrote 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/mimukit/skills/gitkit)<a href="https://agentmods.dev/skills/mimukit/skills/gitkit"><img src="https://agentmods.dev/badge/skills/mimukit/skills/gitkit/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/mimukit/skills/gitkit"><img src="https://agentmods.dev/badge/skills/mimukit/skills/gitkit.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.00138 | $0.08675 |
| Opus 5.5 | $0.00055 | $0.03470 |
| Sonnet 5.5 | $0.00028 | $0.01735 |
| Haiku 4.5 | $0.00014 | $0.00868 |
Grade A, and why
gitkit 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 today.
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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gitkit
One place where the git facts live that every other skill in a toolchain keeps re-deriving: where a worktree goes and what it's named, how it is created, adopted, and removed, which branch is the base, and when to rebase versus merge.
The core here is not clever. All of it is native git worktree, with no vendor CLI, no GUI dependency, and no recorded state anywhere but git's own. That is the point: a laptop with a desktop dev tool and a headless Linux box run identical commands, so there is no second code path to keep in sync and no "degraded mode" to reason about.
One branch of this skill sits outside that core, and says so. Stacked branches drive GitHub's gh stack extension, so that branch alone needs gh and a GitHub remote. It degrades to plain git rather than failing, and nothing else in this file depends on it, so a box with no gh runs everything above untouched.
gitkit is a primitives skill. Most of its runs come from another skill calling it, not from a human saying its name.
When this fires
- worktree. "Spin up a worktree for this branch", "make me a worktree for #42", "where is the worktree for
issue-42-…", "tear down this worktree", "list my worktrees". - base ref. "What's the base branch here", "diff me against the base".
- sync. "Should I rebase or merge here", "sync this branch with main", "this branch is behind, bring it up to date", "make this PR review-ready on the latest base".
- clean. "Clean up my merged worktrees", "which branches can I delete", "this repo is full of dead branches".
- rescue. "I lost a commit", "my rebase ate my work", "I reset the wrong branch", "what's in this stash".
- stack. "Stack this on #43", "start #44 on top of #43's branch", "restack this chain", "show me the stack".
- called by another skill. Any skill that needs a worktree, a base ref, a branch name, or a sync decision delegates here and uses what comes back.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +2 lines d615d480d061
- 2d ago Changed · +27 lines b00f37096fed
- 3d ago Changed · -1 lines df4e26894165
- 4d ago Changed · +30 lines d9fc2055fadc
- 21d ago Changed · +26 lines · -73 tokens per session 711c02c56a22
- 1mo ago Changed · +1 lines 77cccb7fcc9c
- 1mo ago Changed · +1 lines 587a70e205be
- 1mo ago First seen · 277 lines · 211 tokens per session scan A 6222ba9c152b
gitkit is a skill published in the GitHub repository mimukit/skills (2 stars, last pushed yesterday), licensed MIT. It adds 138 tokens to every session and 8,675 once invoked, about $0.0006 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
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.