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 xbklairith/kisune --skill git-workflowgit clone --depth 1 https://github.com/xbklairith/kisuneWrote 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/xbklairith/kisune/git-workflow)<a href="https://agentmods.dev/skills/xbklairith/kisune/git-workflow"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/git-workflow/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/xbklairith/kisune/git-workflow"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/git-workflow.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.00053 | $0.01448 |
| Opus 5.5 | $0.00021 | $0.00579 |
| Sonnet 5.5 | $0.00011 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
git-workflow 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 8d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
Purpose
Manage git operations with best practices, generating meaningful commit messages, managing branches safely, creating comprehensive pull requests, and preventing common git mistakes.
Activation Triggers
Activate this skill when:
- User says "commit my changes"
- User mentions "create a branch"
- User asks to "create a PR" or "pull request"
- User says "push to remote"
- Before any destructive git operation
- User mentions git or version control
Core Capabilities
1. Smart Commits
Goal: Generate meaningful, consistent commit messages that explain WHY changes were made
Process:
- Analyze Changes — Run
git statusandgit diff - Understand Intent — What was added/modified/removed? What problem does this solve?
- Generate Commit Message using format:
[type]: [concise description in present tense]
Commit Types:
featorfeature- New featurefix- Bug fixrefactor- Code restructuring without behavior changetest- Adding or updating testsdocs- Documentation changeschore- Maintenance tasks (deps, config, etc.)style- Code formatting (no logic change)perf- Performance improvements
Message Guidelines:
- Present tense, imperative mood ("Add" not "Added")
- Focus on WHAT and WHY, not HOW
- Under 72 characters for first line
- No period at the end
Good examples:
feat: Add RSI indicator to market analysis
fix: Handle division by zero in position sizing
refactor: Extract strategy validation into separate function
Avoid: Vague messages ("updated files"), past tense ("Added new stuff"), or non-descriptive ("WIP", "asdfgh").
- Show and Confirm — Present proposed message, list of files, and ask for approval
- Execute and Verify — Stage files, commit, verify with
git log -1 --oneline
2. Branch Management
Naming Convention: [type]/[description]
| Type | Purpose | Example |
|---|---|---|
feature/ |
New features | feature/user-authentication |
fix/ |
Bug fixes | fix/login-timeout-error |
refactor/ |
Code restructuring | refactor/payment-processing |
experiment/ |
Experimental work | experiment/ml-price-prediction |
hotfix/ |
Urgent production fixes | hotfix/security-vulnerability |
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.
- 8d ago Changed · -7 lines c83dc2ea8ca2
- 10d ago Changed · +28 tokens per session 94250bb33ae6
- 1mo ago Changed 98e37b5f5237
- 1mo ago First seen · 175 lines · 25 tokens per session scan A cdab8916ff6d
git-workflow is a skill published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 53 tokens to every session and 1,448 once invoked, about $0.0002 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.
Other skills, from other repositories
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.