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/martinkuhne/devstack/git-operationsnpx skills add MartinKuhne/devstack --skill git-operationsgit clone --depth 1 https://github.com/MartinKuhne/devstackWhat 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.00018 | $0.00473 |
| Opus 5 | $0.00009 | $0.00236 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 yesterday.
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
What I do
I provide guidance and best practices for Git operations, focusing on:
- Creating and managing feature branches
- Making commits with meaningful messages
- Branch naming conventions
- Handling merge conflicts
- Keeping branches up-to-date with main
Branch Naming Convention
Use this format for feature branches:
feature/<ticket-id>-<short-description>
feature/ai-123-add-user-auth
bugfix/456-fix-login-error
hotfix/789-security-patch
Commit Message Format
Follow conventional commits:
<type>(<scope>): <subject>
<body>
<footer>
Types: feat, fix, docs, style, refactor, test, chore
Example:
feat(auth): add OAuth2 authentication support
- Implement Google OAuth2 flow
- Add token refresh logic
- Update user model with provider field
Closes #123
Working with Feature Branches
Create and Switch
git checkout -b feature/123-add-auth
Update from Main
git fetch origin
git rebase origin/main
Commit Changes
git add <files>
git commit -m "feat(scope): description"
Push Branch
git push -u origin feature/123-add-auth
Merge Conflict Resolution
- Identify conflicting files:
git status
- Open conflicting files and resolve marked sections:
your changes
=======
incoming changes
>>>>>>> branch-name
- After resolving, stage and commit:
git add <resolved-files>
git commit
Best Practices
- Commit early and often with clear messages
- Keep commits atomic (one logical change per commit)
- Rebase over merge when updating from main
- Use
--force-with-leasewhen force pushing (never--force) - Delete merged branches after PR approval
- Always pull latest main before creating new feature branches
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.
- yesterday First seen · 107 lines · 18 tokens per session scan A 00b01808e3d8
git-operations is a skill published in the GitHub repository MartinKuhne/devstack (2 stars, last pushed 20d ago), licensed MIT. It adds 18 tokens to every session and 473 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…