A Git workflow for saving code changes, reviewing them, and sharing them with a team. Git is a tool that records code history and supports collaboration.

It helps scan changes for credentials, decide whether to split work into multiple commits, write commit messages, and isolate work in separate Git worktrees.

It reduces accidental commits, leaked secrets, and confusing groups of unrelated changes.

git — Skill by nguyenthienthanh

Install

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.

agentmods

npx agentmods add skills/nguyenthienthanh/aura-frog/git

Any agent

npx skills add nguyenthienthanh/aura-frog --skill git

Clone the repo

git clone --depth 1 https://github.com/nguyenthienthanh/aura-frog

Made for: Claude Code, Codex.

Or install aura-frog, the plugin that ships this one along with the rest of its 17 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 851 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00035	$0.00851
Opus 5	$0.00017	$0.00426
Sonnet 5	$0.00007	$0.00170
Haiku 4.5	$0.00003	$0.00085

Measured 3d ago against content hash a7d9317880a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

aura-frog/skills/git/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.

Git

Token-efficient git operations (commit/PR flow) plus worktree isolation for workflows.

Commit workflow (security scan + auto-split)

Token-efficient git: 2-4 tool calls max.

1. Stage + Security Scan

Stage files, check diff stats, scan for secrets (api_key|token|password|secret|credential). If secrets found: STOP. Show matches. Block commit.

2. Split Decision

Split if: mixed types (feat+fix), FILES >10 unrelated, multiple scopes (frontend+backend). Single if: same type/scope, FILES ≤3 + LINES ≤50, logically related.

3. Commit Message

Format: type(scope): description (<72 chars, present tense, imperative) Types: feat, fix, docs, chore, refactor, test, perf

4. Confirm → Commit → Push

NEVER auto-commit or auto-push (per rules/workflow/git-workflow.md):

Show git diff --stat + the proposed commit message
Wait for explicit user confirmation before git commit
After commit, ask before git push separately — push only if user requests

No exceptions.

PR Workflow

git fetch origin main + log commits since main + diff stats
gh pr create --title "type(scope): description" --body "## Summary\n- bullets\n\n## Test Plan\n- steps"

Output

staged: 3 files (+45/-12 lines) | security: passed | commit: a3f8d92 feat(auth): add token refresh

Worktree isolation

Auto-create git worktree when starting a workflow. All changes on isolated branch. Discard on failure -- zero damage to main.

When to Use

Auto: /run when AF_WORKTREE=true
Manual: User says "use a worktree"
Skip: Quick fixes, config changes, single-file edits

Lifecycle

worktree_lifecycle[5]{event,action}:
  run:start,"git worktree add .worktrees/[id] -b af/[id]"
  Phase 1 approved,All edits in worktree directory
  Phase 5 complete,"Offer: merge / create PR / keep branch / discard"
  run:cancel,"git worktree remove .worktrees/[id]"
  run failed,Discard worktree — main untouched

Read the full file on GitHub · 114 lines

Changes

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.

3d ago First seen · 114 lines · 35 tokens per session scan A a7d9317880a2

Subscribe to this mod's changes

git is a skill published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 851 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.

Git and workflow ai-assisted-development ai-for-developers claude-code code-quality context-engineering developer-productivity

openspec-plus-apply

MANDATORY skill that activates whenever the OpenSpec apply phase begins. Triggers: /opsx-apply runs, the openspec-apply-change vanilla skill is referenced or active, openspec instructions apply is invoked, or the user asks to implement, apply, execute, or build out an OpenSpec change ('implement the change', 'apply…

sudokar/openspec-plus · 110 tokens

openspec-plus-design

MANDATORY skill that activates whenever the OpenSpec design phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions design is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec design…

sudokar/openspec-plus · 82 tokens

openspec-plus-spec

MANDATORY skill that activates whenever the OpenSpec specification phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions spec or openspec instructions specs is invoked; or the user wants to create, update, review…

sudokar/openspec-plus · 88 tokens

openspec-plus-tdd

MANDATORY skill that activates whenever code is written to implement an OpenSpec change task. Triggers: openspec-plus-apply is active, /opsx-apply is running, the user is implementing tasks from an OpenSpec change, an implementer subagent dispatched by openspec-plus-apply is starting work, or the user invokes phrases…

sudokar/openspec-plus · 190 tokens

openspec-plus-proposal

MANDATORY skill that activates whenever the OpenSpec proposal phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions proposal is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec…