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/batteryshark/rekitnpx agentmods add skills/batteryshark/rekit/gitopsWrote 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/batteryshark/rekit/gitops)<a href="https://agentmods.dev/skills/batteryshark/rekit/gitops"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/gitops/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/batteryshark/rekit/gitops"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/gitops.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.00181 | $0.01500 |
| Opus 5.5 | $0.00072 | $0.00600 |
| Sonnet 5.5 | $0.00036 | $0.00300 |
| Haiku 4.5 | $0.00018 | $0.00150 |
Grade A, and why
gitops 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations
A safe, structured wrapper over git for harnesses (or smaller models) that need to
use version control without knowing git's syntax, refspecs, or worktree plumbing.
You call plain verbs; the skill runs git non-interactively and hands back one JSON
object describing what happened.
When to use
Reach for this when an agent needs to commit, branch, stash, push, or set up a
worktree, but you don't want it improvising raw git — e.g. a model that knows it
should "save my work on a new branch" but would fumble git switch -c, git add,
git commit, upstream tracking, or git worktree add. It removes whole classes of
footguns: no interactive prompts, no accidental --force, structured errors instead
of raw git stderr.
It operates on your own trusted repo — it does not analyse or execute samples.
How it works
gitops <op> [args]. Every op prints exactly one line of JSON to stdout:
{"ok": true, "op": "commit", "commit": "a1b2c3d", "branch": "feature-x", ...}
{"ok": false, "op": "commit", "error": "nothing to commit (no staged changes)", "hint": "..."}
So a caller never parses git's human output — it reads ok, then the fields it needs.
Add -C <dir> to any op to target a repo other than the current directory.
Operations
| op | what it does |
|---|---|
status |
branch, upstream, ahead/behind, and staged / unstaged / untracked file lists |
log [-n N] |
recent commits (hash, subject, author, when) |
diff [--staged] [paths] |
a diff as text, plus a --stat summary |
branches |
local branches + which is current |
add [paths] |
stage paths (default: everything) |
commit "<msg>" [--path ...] [--author ...] |
stage (all by default) then commit; returns the new hash |
branch <name> [start] |
create a new branch and switch to it |
switch <name> |
switch to an existing branch |
stash [-m msg] [-u] |
stash uncommitted changes (-u includes untracked) |
stash-pop / stash-list |
restore the latest stash / list stashes |
push [--remote origin] [--force] |
push the current branch; sets upstream automatically on first push |
pull [--rebase] / fetch [--remote] |
sync with the remote |
clone <url> [dir] [--branch B] [--depth N] |
clone a remote repo into a new directory |
remote-add <url> [--name origin] |
add a remote to the current repo (default name origin) |
remotes |
list configured remotes (name → url) |
merge <branch> [--no-ff] [-m msg] / merge --abort |
merge a branch into the current one; conflicts come back as {conflicts:[...]} |
cherry-pick <commit> / cherry-pick --abort |
apply one commit onto the current branch |
tag <name> [-m msg] [--ref] [--delete] [--push] |
create (annotated if -m), delete, or push a tag |
tags |
list tags (newest first) |
worktree-add <path> (--branch B | --new-branch B [--start]) |
check a branch out into another directory |
worktree-list / worktree-remove <path> --force |
list / remove worktrees |
undo |
undo the last commit but keep its changes (soft reset — safe) |
discard [paths] --force |
destructive: drop uncommitted changes |
reset-hard [ref] --force |
destructive: move HEAD + working tree to ref |
init [path] [--initial-branch main] |
start a new repo |
What ships with it
1 file 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.
- 1mo ago First seen · 94 lines · 181 tokens per session scan A 03b8b99f8496
gitops is a skill published in the GitHub repository batteryshark/rekit (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 181 tokens to every session and 1,500 once invoked, about $0.0007 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-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.