Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add asfbay-bit/opchain-skills/plugin install opchainWrote 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/asfbay-bit/opchain-skills/oc-git-ops)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-git-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-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/skills/asfbay-bit/opchain-skills/oc-git-ops"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-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.00125 | $0.06590 |
| Opus 5 | $0.00063 | $0.03295 |
| Sonnet 5 | $0.00025 | $0.01318 |
| Haiku 4.5 | $0.00013 | $0.00659 |
Grade A, and why
oc-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 4d 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 — 670 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Ops
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Move code from Claude's workspace to a git repository with proper branch management, commit structure, and PR descriptions. This is the bridge between "Claude built it" and "it's in version control."
/oc-git-ops — Command Reference
When the user types /oc-git-ops, display this menu:
GIT OPS COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WORKFLOW
/oc-git-init Clone repo + set up workspace for a project
/git-branch Create a feature branch from convention
/oc-git-commit Stage + commit with structured message
/oc-git-pr Generate PR description from commits/checkpoint
/git-push Push branch to remote
/oc-git-sync Full workflow: branch → commit → push → PR
/oc-git-release Tag a merged release + push the tag (closes the ledger)
UTILITIES
/oc-git-status Show current branch, staged changes, remote state
/git-diff Show what's changed since last commit
/oc-git-convention Show/set naming conventions for this project
/checkpoint Show checkpoint status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-git-ops to see this again.
How This Skill Works
CLAUDE WORKSPACE GIT REPO
/home/claude/project/ github.com/user/project
Built files ──────► Feature branch
+ checkpoint data ──────► Structured commits
+ audit report ──────► PR description
The typical flow:
- Clone the user's repo (or confirm it's already cloned)
- Create a feature branch following project conventions
- Copy/move built files into the repo working tree
- Make structured commits (one per logical unit)
- Push the branch
- Run the pre-PR gate: oc-docs-forge (PR docs packet) → oc-repo-ops (readiness check)
- Generate a PR description from the checkpoint + commit log + docs packet
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.
- 4d ago Changed 2bc179a6b0b4
- 7d ago First seen · 670 lines · 125 tokens per session scan A 9a6df80ce7fe
oc-git-ops is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 125 tokens to every session and 6,590 once invoked, about $0.0006 per session on Opus 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
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.