A commit workflow that checks changed files and records them in Git using a consistent message format.

Use it when work is reviewed and ready to save as a Git commit. It stages named files, checks recent commit style, and creates the commit without sending it to a remote repository.

It helps prevent unfinished work, sensitive files, or broad unintended changes from entering the project history. It also keeps commit messages predictable for people reviewing the code later.

git-save — Skill by brolag

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/brolag/neural-claude-code/git-save

Any agent

npx skills add brolag/neural-claude-code --skill git-save

Clone the repo

git clone --depth 1 https://github.com/brolag/neural-claude-code

Made for: Claude Code, Codex.

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

When invoked 316 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.00056	$0.00316
Opus 5	$0.00028	$0.00158
Sonnet 5	$0.00011	$0.00063
Haiku 4.5	$0.00006	$0.00032

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

Security

Grade A, and why

git-save 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 2d 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.

skills/git-save/SKILL.md · 34 lines

What it actually says

/git-save — Commit Workflow

git status — identify changed files
git diff — understand what changed
git log --oneline -5 — match existing commit style
Stage specific files by name (never git add -A)
Skip files that look sensitive (.env, credentials, keys)
Draft commit: type(scope): description

Commit Types

type	when
`feat`	new feature
`fix`	bug fix
`refactor`	restructure, no behavior change
`docs`	documentation only
`test`	tests added/updated
`chore`	build, deps, config

Rules

NEVER commit if tests are failing
NEVER commit .env or credential files
NEVER auto-push (commit only, user pushes manually)
Ask before committing if scope is unclear

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.

2d ago First seen · 34 lines · 56 tokens per session scan A 2c0d086b5421

Subscribe to this mod's changes

git-save is a skill published in the GitHub repository brolag/neural-claude-code (11 stars, last pushed 12d ago), licensed MIT. It adds 56 tokens to every session and 316 once invoked, about $0.0003 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.

Code review Git and workflow Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens