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/gullitmiranda/.cursor/gitnpx skills add gullitmiranda/.cursor --skill gitgit clone --depth 1 https://github.com/gullitmiranda/.cursorWhat 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 | $0.00047 | $0.02084 |
| Opus 5 | $0.00023 | $0.01042 |
| Sonnet 5 | $0.00009 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
git 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 2d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/commit - Smart Git Commit
Overview
You are a git commit specialist that creates conventional commits with automatic type detection and safety checks.
Steps
-
Branch Safety Check:
- Check if currently on main/master branch
- If yes and using
/commit(without--mainflag), automatically create a feature branch based on the changes detected - If using
/commit --main, allow direct commit to main/master branch (emergency fixes only)
-
Analyze Changes:
- Run
git statusandgit diff --cached(orgit difffor all changes if--allflag is used) - Detect conventional commit type from changes:
feat: New features, components, functionalityfix: Bug fixes, error correctionschore: Dependencies, build, config, toolingdocs: Documentation changesstyle: Code formatting, style changesrefactor: Code restructuring without behavior changetest: Adding or updating tests
- Check for Linear issue references in commit message or staged changes
- Run
-
Generate Commit Message:
- Format:
<type>(<scope>): <description> - Scope should be component/area affected (optional)
- Description should be concise and clear
- Use present tense, imperative mood
- Include Linear issue references (e.g.,
ENG-123,PROJ-456) in description for auto-linking
- Format:
-
Execute Commit:
- Use heredoc format for multi-line commit messages
- Commit only staged changes (unless
--allflag is used) - If
--allflag is used, stage and commit all changes (unstaged + staged) - Confirm successful commit with git log
-
Validation:
- Ensure commit follows conventional format
- Verify only intended changes were committed
Auto Branch Creation
When on main/master branch and using /commit (without --main flag):
- Analyze Changes: Detect commit type from staged/unstaged changes
- Generate Branch Name:
- For features:
feature/<type>-<short-description> - For fixes:
fix/<short-description> - For chores:
chore/<short-description> - For docs:
docs/<short-description>
- For features:
- Create Branch:
git checkout -b <generated-branch-name> - Proceed with Commit: Continue with normal commit process
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.
- 2d ago First seen · 334 lines · 47 tokens per session scan A acfccc78bd88
git is a skill published in the GitHub repository gullitmiranda/.cursor (2 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 2,084 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…