git-operations

git-operations is a skill for Claude Code, Codex from Yoshikemolo/mcp-jira-devflow. It costs 31 tokens per session (449 once invoked), scanned A, original, MIT.

A helper for Git, the version-control system used to track code changes. It supports branches, commits, syncing with remote repositories, and viewing status, history, and differences.

In plain words
What is it for?
Use it to create branches, commit and push work, pull updates, inspect diffs and logs, and manage repository state.
Why use it?
It provides a consistent workflow for changing shared code while requiring approval for risky operations such as force-pushing or permanently discarding changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create branches, commit and push work, pull updates, inspect diffs and logs, and manage repository state.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yoshikemolo/mcp-jira-devflow/git-operations
Install

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.

Any agent
npx skills add Yoshikemolo/mcp-jira-devflow --skill git-operations
Clone the repo
git clone --depth 1 https://github.com/Yoshikemolo/mcp-jira-devflow

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for git-operations

README.md
[![agentmods](https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/git-operations/github.svg)](https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/git-operations)
Your own site
<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/git-operations"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/git-operations/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.

agentmods 80×15 button for git-operations

Your own site · 80×15
<a href="https://agentmods.dev/skills/yoshikemolo/mcp-jira-devflow/git-operations"><img src="https://agentmods.dev/badge/skills/yoshikemolo/mcp-jira-devflow/git-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 449 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00449
Opus 5.5 $0.00012 $0.00180
Sonnet 5.5 $0.00006 $0.00090
Haiku 4.5 $0.00003 $0.00045

Measured 1mo ago against content hash 7511cb6e1a37, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-operations 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.

skills/git-operations/SKILL.md · 87 lines

What it actually says

Git Operations Skill

Version control operations for Git repositories.

Allowed Operations

  • Clone repositories
  • Create branches
  • Switch branches
  • Commit changes
  • Push to remote
  • Pull from remote
  • Fetch updates
  • View status, log, diff

Forbidden Operations

These require explicit user approval:

  • Force push (--force)
  • Rebase
  • Reset --hard
  • Delete remote branches
  • Modify git hooks
  • Change git config globally

Constraints

  • No direct commits to main or master
  • Branch names must follow convention
  • Commit messages must follow conventional commits

Quick Branch Reference

<type>/<issue-id>-<short-description>

feature/PROJ-123-add-login
fix/PROJ-456-null-pointer
chore/update-dependencies

Types: feature, fix, chore, docs, refactor

For complete naming rules, see BRANCH-NAMING.md.

Quick Commit Reference

<type>(<scope>): <description>

feat(auth): add login endpoint
fix(api): handle null response
docs(readme): update setup guide

Types: feat, fix, docs, style, refactor, test, chore

For complete format, see COMMIT-CONVENTIONS.md.

Safety Checks

Before any operation:

  1. Verify working directory is clean
  2. Verify on correct branch
  3. Check for uncommitted changes

Example Usage

Create branch feature/PROJ-123-user-auth
Commit changes with message "feat(auth): add login endpoint"
Push current branch to origin
Show git status and recent commits
Files

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.

Changes

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.

  1. 1mo ago First seen · 87 lines · 31 tokens per session scan A 7511cb6e1a37

Subscribe to this mod's changes

git-operations is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 449 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

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.

travisjneuman/.claude · 52 tokens

apply

Apply a prior /repo-fleet-hygiene:audit action-plan JSON behind one fleet confirmation: default dry-run re-derives branch/worktree tips and prints the ordered batch; --apply mutates only after interactive confirmation or --yes. Owns batched merged-local-branch deletion with fail-closed OID refresh; cleans…

melodic-software/claude-code-plugins · 109 tokens

git-workflow

Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.

TheBeardedBearSAS/claude-craft · 0 tokens

commit-context

Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", "who wrote this", or wants context on a specific location in the codebase.

rohitg00/agentmemory · 61 tokens

commit-history

List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.

rohitg00/agentmemory · 49 tokens

feature-publish

Commit the feature, write the PR body, publish in the selected mode, and drive the PR.

omnigent-ai/omnigent · 24 tokens