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/0xDarkMatter/claude-modsWrote 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/commands/0xdarkmatter/claude-mods/git-ops)<a href="https://agentmods.dev/commands/0xdarkmatter/claude-mods/git-ops"><img src="https://agentmods.dev/badge/commands/0xdarkmatter/claude-mods/git-ops/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/commands/0xdarkmatter/claude-mods/git-ops"><img src="https://agentmods.dev/badge/commands/0xdarkmatter/claude-mods/git-ops.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.00050 | $0.00827 |
| Opus 5.5 | $0.00020 | $0.00331 |
| Sonnet 5.5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
git-ops 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/git-ops — git + worktree orchestrator
Thin command wrapper over the git-ops skill. The skill owns the logic
(SKILL.md, scripts/); this command just routes $ARGUMENTS to the right mode.
Arguments
$ARGUMENTS
| Invocation | Mode |
|---|---|
/git-ops --landall (aliases: landall, land-all, land all) |
Land all — survey → classify → confirm → batch-land |
/git-ops (no args) |
Status survey (status.sh + worktree-survey.sh) |
/git-ops <anything else> |
Pass the request to the git-ops skill as-is |
Always invoke the git-ops skill (Skill tool) first, then follow the branch below.
--landall — batch-land every pending lane
This is the front-door for "I've got 4-5 chips/sessions/worktrees, land the ones that are done." git-ops discovers + classifies; fleet-ops executes the sequential, test-gated landing. Follow the skill's "Land all" section exactly. The flow, in short:
-
Survey (read-only). Run:
bash $HOME/.claude/skills/git-ops/scripts/land-all.sh --porcelainPass
--recent-days Nthrough from$ARGUMENTSif the user gave one (their lanes may span longer than the 7-day default); pass--active-window Nto tune the live-writer threshold. Each branch is classified LANDABLE / STALE / WIP / ACTIVE / MERGED. -
Confirm the plan (
AskUserQuestion, required). Present three groups — land these LANDABLE / park these WIP+ACTIVE+STALE / prune these MERGED — and get an explicit go. Surface anyfar behind (N)notes so the user knows which lands may conflict. Never land without this confirm: it writes to the trunk. -
Execute via fleet-ops (only the confirmed landable set):
bash $HOME/.claude/skills/fleet-ops/scripts/fleet.sh track <landable-branches...> bash $HOME/.claude/skills/fleet-ops/scripts/fleet.sh land --all --runningLands oldest-first, through the test gate, auto-rebasing the rest after each.
-
Escalate conflicts — never auto-resolve. A
CONFLICTlane is reported, not guessed. Offer: resolve in the lane, skip, orfleet revert <branch>.
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 · 66 lines · 50 tokens per session scan A 02706c54647b
git-ops is a command published in the GitHub repository 0xDarkMatter/claude-mods (66 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 827 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-30.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
branch
Show Claude Code costs per git branch / PR.
versioning
Universal version file discovery and sync. Works with any project structure.