commit-workflow

commit-workflow is a skill for Claude Code, Codex from jscott3201/ai-agent-skills. It costs 35 tokens per session (1,304 once invoked), scanned A, original, no licence file.

A workflow for recording Git commits in a shared project graph. Git is a system for tracking code changes, and a commit is a saved set of changes.

In plain words
What is it for?
Use it to verify work, link commits to project context, merge commit records, and avoid pushing changes unless asked.
Why use it?
It keeps commits connected to the milestones, discoveries, and decisions they relate to, while adding checks before committing.

Skill for Claude CodeCodex

Part of the justin-tools plugin — 26 skills, 9 agents, 4 hooks shipped together

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/jscott3201/ai-agent-skills/commit-workflow
Any agent
npx skills add jscott3201/ai-agent-skills --skill commit-workflow
Clone the repo
git clone --depth 1 https://github.com/jscott3201/ai-agent-skills

Made for: Claude Code, Codex.

Or install justin-tools, the plugin that ships this one along with the rest of its 26 skills, 9 agents, 4 hooks.

Wrote 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.

agentmods badge for commit-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/jscott3201/ai-agent-skills/commit-workflow.svg)](https://agentmods.dev/skills/jscott3201/ai-agent-skills/commit-workflow)
Your own site
<a href="https://agentmods.dev/skills/jscott3201/ai-agent-skills/commit-workflow"><img src="https://agentmods.dev/badge/skills/jscott3201/ai-agent-skills/commit-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.01304
Opus 5 $0.00017 $0.00652
Sonnet 5 $0.00007 $0.00261
Haiku 4.5 $0.00003 $0.00130

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

Security

Grade A, and why

commit-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 4d 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/commit-workflow/SKILL.md · 191 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. 4d ago First seen · 191 lines · 35 tokens per session scan A e3c7a0d8279c

Subscribe to this mod's changes

commit-workflow is a skill published in the GitHub repository jscott3201/ai-agent-skills (2 stars, last pushed 4mo ago), with no licence file. It adds 35 tokens to every session and 1,304 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-31.

Related

Other skills, from other repositories

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

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

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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