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 DaleStudy/skills --skill gitgit clone --depth 1 https://github.com/DaleStudy/skillsWrote 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/dalestudy/skills/git)<a href="https://agentmods.dev/skills/dalestudy/skills/git"><img src="https://agentmods.dev/badge/skills/dalestudy/skills/git/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/dalestudy/skills/git"><img src="https://agentmods.dev/badge/skills/dalestudy/skills/git.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.00132 | $0.03497 |
| Opus 5.5 | $0.00053 | $0.01399 |
| Sonnet 5.5 | $0.00026 | $0.00699 |
| Haiku 4.5 | $0.00013 | $0.00350 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git
Git 버전 관리 모범 관례 및 워크플로우 가이드.
커밋 메시지 컨벤션
Conventional Commits 사용
커밋 메시지는 <type>: <description> 형식을 따른다:
feat: add form validation to login page
fix: prevent duplicate email check error on signup
docs: add installation guide to README
refactor: extract auth logic into separate module
test: add payment feature tests
chore: update dependencies
주요 타입
| 타입 | 설명 | 예시 |
|---|---|---|
feat |
새로운 기능 추가 | feat: add dark mode support |
fix |
버그 수정 | fix: prevent token deletion on logout |
docs |
문서 변경 (코드 변경 없음) | docs: update API documentation |
style |
코드 포맷팅, 세미콜론 누락 (동작 변경 X) | style: apply ESLint rules |
refactor |
리팩토링 (기능 변경 없음) | refactor: extract utility functions |
test |
테스트 코드 추가/수정 | test: add login API tests |
chore |
빌드, 설정 변경 (src 변경 없음) | chore: update Webpack config |
perf |
성능 개선 | perf: implement lazy loading for images |
상세 형식 (선택사항)
<type>(<scope>): <subject>
<body>
<footer>
예시:
feat(auth): implement JWT-based authentication
- Issue access and refresh tokens
- Store refresh tokens in Redis
- Add token renewal API endpoint
Closes #123
자주 하는 실수
# ❌ 타입 누락
git commit -m "bug fix"
# ❌ 모호한 설명
git commit -m "fix: fix issue"
# ❌ 한 커밋에 여러 작업
git commit -m "feat: implement login, signup, and password reset"
# ✅ 명확하고 단일 책임
git commit -m "feat: add form validation to login page"
커밋 메시지 작성 가이드라인
- 첫 줄은 50자 이내 - 간결한 요약
- 현재형 사용 - "added" (X) → "add" (O)
- 명령형 어조 - "adds" (X) → "add" (O)
- 첫 글자 소문자 -
Feat:(X) →feat:(O) - 마침표 금지 -
feat: add feature.(X) →feat: add feature(O) - 본문은 72자마다 줄바꿈 - 가독성 향상
- Why > What - 변경한 내용보다 변경한 이유를 설명
- 영어로 작성 - 릴리즈 노트 생성 도구와의 호환성을 위해
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 · 478 lines · 132 tokens per session scan A 39ad99dfe164
git is a skill published in the GitHub repository DaleStudy/skills (4 stars, last pushed 3d ago), licensed MIT. It adds 132 tokens to every session and 3,497 once invoked, about $0.0005 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
commit-work
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.