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.
npx agentmods add skills/yoshikemolo/mcp-jira-devflow/git-operationsnpx skills add Yoshikemolo/mcp-jira-devflow --skill git-operationsgit clone --depth 1 https://github.com/Yoshikemolo/mcp-jira-devflowWrote 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/yoshikemolo/mcp-jira-devflow/git-operations)<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="Measured on agentmods" 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.00031 | $0.00449 |
| Opus 5 | $0.00015 | $0.00225 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
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 6d 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.
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
mainormaster - 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:
- Verify working directory is clean
- Verify on correct branch
- 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
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.
- 6d ago First seen · 87 lines · 31 tokens per session scan A 7511cb6e1a37
git-operations is a skill published in the GitHub repository Yoshikemolo/mcp-jira-devflow (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 449 once invoked, about $0.0002 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
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
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…
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests. Use when user asks to "add pre-commit hooks", "setup husky", "setup pre-commit", "configure lint-staged", or wants commit-time formatting/typechecking/testing. Don't use for running linters manually or writing tests.
commit
Group unstaged changes into atomic commits by concern, following repository style. Use when user asks to "commit", "create a commit", "commit changes", or "/commit". Don't use for pushing (that belongs to /ship) or creating pull requests.
git-commit
Commit work the right way by gathering full repo state, respecting the project's commitlint/pre-commit/branch rules, staging only understood files, and writing a conventional-commit message whose body explains why. Use when committing, branching, or pushing changes.