commit-push

A workflow for committing the changes made during the current chat session and sending them to the current Git branch. It uses Conventional Commits, a standard format for writing commit messages.

In plain words
What is it for?
Use it after completing code changes when you want them committed and pushed. It is for changes made in the current chat session and the branch currently checked out.
Why use it?
It groups the session's work into a recorded Git commit and updates the remote branch, reducing the manual steps needed to save and share changes.

Skill for Claude CodeCodexCursor

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

Made for: Claude Code, Codex, Cursor.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 68 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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00068
Opus 5 $0.00014 $0.00034
Sonnet 5 $0.00005 $0.00014
Haiku 4.5 $0.00003 $0.00007

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

Security

Grade A, and why

commit-push 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.

.cursor/skills/commit-push/SKILL.md · 9 lines

What it actually says

Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.

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. 2d ago First seen · 9 lines · 27 tokens per session scan A 1b82155a0d3f

Subscribe to this mod's changes

commit-push is a skill published in the GitHub repository DataCovey/nornweave (27 stars, last pushed 5d ago), licensed Apache-2.0. It adds 27 tokens to every session and 68 once invoked, about $0.0001 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.