Borrowing it
Nothing to install: this file belongs to kissrosecicd-hub/agents-evolution. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kissrosecicd-hub/agents-evolution/main/.agents/skills/scientiacapital-git-workflow/SKILL.mdgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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/kissrosecicd-hub/agents-evolution/scientiacapital-git-workflow)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/scientiacapital-git-workflow"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/scientiacapital-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/kissrosecicd-hub/agents-evolution/scientiacapital-git-workflow"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/scientiacapital-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.00040 | $0.03198 |
| Opus 5 | $0.00020 | $0.01599 |
| Sonnet 5 | $0.00008 | $0.00640 |
| Haiku 4.5 | $0.00004 | $0.00320 |
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 9d 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 — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill complements worktree-manager-skill (which handles parallel development) by providing the conventions for commits and PRs within those worktrees.
<quick_start> Conventional Commit format:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
Example:
git commit -m "feat(auth): add JWT refresh token rotation
Implements automatic token refresh 5 minutes before expiry.
Closes #123"
Branch naming: <type>/<ticket>-<short-description>
git checkout -b feat/AUTH-123-refresh-tokens
</quick_start>
<success_criteria> Git workflow is successful when:
- All commits follow conventional commit format
- Branch names follow
<type>/<ticket>-<description>pattern - PRs use consistent template with summary, test plan, and checklist
- Merge strategy matches branch type (squash for features, merge for releases)
- Commit history tells a clear story of changes
- No force pushes to main/master without explicit team agreement </success_criteria>
<conventional_commits>
Conventional Commits Specification
Based on conventionalcommits.org
Commit Types
| Type | Description | Changelog Section | Version Bump |
|---|---|---|---|
| feat | New feature | Features | Minor |
| fix | Bug fix | Bug Fixes | Patch |
| docs | Documentation only | - | - |
| style | Formatting, no code change | - | - |
| refactor | Code change, no feature/fix | - | - |
| perf | Performance improvement | Performance | Patch |
| test | Adding/fixing tests | - | - |
| build | Build system changes | - | - |
| ci | CI configuration | - | - |
| chore | Maintenance tasks | - | - |
What ships with it
2 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.
- 9d ago First seen · 496 lines · 40 tokens per session scan A a9aa23a3d455
git-workflow is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 3,198 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…