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 skills add emaraschio/cursor-commands --skill fix-git-issuesgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/emaraschio/cursor-commands/fix-git-issues)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/fix-git-issues"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/fix-git-issues/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/emaraschio/cursor-commands/fix-git-issues"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/fix-git-issues.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.00013 | $0.00336 |
| Opus 5.5 | $0.00005 | $0.00134 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
fix-git-issues 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.
What it actually says
Overview
Help resolve common Git problems and conflicts with step-by-step commands and explanations for each situation.
Steps
- Merge Conflicts
- Analyze conflicting changes and their context
- Provide resolution strategies for different conflict types
- Suggest the best approach to preserve important changes
- Generate resolved code maintaining functionality
- Branch Management
- Help with branch cleanup and organization
- Suggest rebasing vs merging strategies
- Assist with cherry-picking specific commits
- Guide through complex branch operations
- Commit History
- Help with commit message improvements
- Assist with squashing and organizing commits
- Guide through interactive rebase operations
- Fix commit authorship and metadata
- Repository Issues
- Help recover from detached HEAD state
- Assist with undoing commits and changes
- Guide through stash management
- Resolve submodule and remote issues
Git Issues Checklist
- Problem identified and analyzed
- Git commands provided with explanations
- Resolution strategy validated
- Changes tested and verified
- Repository state clean and functional
Guardrails
- Get explicit consent before destructive git commands (reset, rebase, or history rewrite).
- Never force-push main or a shared branch without an explicit request.
- Explain each command before running it.
- Never print or commit secrets or credential files (.env, .env.*, keys); flag any exposure instead of committing it.
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.
- 1mo ago First seen · 46 lines · 13 tokens per session scan A 0b75ade219a4
fix-git-issues is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 336 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-09-03.
Other skills, from other repositories
housekeep-dead-code
Remove dead code by category — one commit each, typecheck and tests between, bisect on red — then add a Knip ratchet. Use when "delete the dead code", "remove unused files", or "wire up Knip". Audit first → plan-dead-code. README/deps → workflow-housekeep.
git-onboarding-auto
A Git setup and pull-request workflow automation skill. Git is the version-control tool developers use to track code changes, while a pull request is a request for teammates to review and merge those changes.
commit
Generate a conventional commit message for staged changes.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.