prp-core-commit

A command that creates one focused Git commit with a conventional commit message, such as "fix: handle empty input".

In plain words
What is it for?
Use it to commit selected or uncommitted files with short, lowercase messages describing a feature, fix, test, documentation change, refactor, or maintenance task.
Why use it?
It keeps related changes grouped, makes commit history easier to read, and helps avoid committing unrelated files together.

Command for Claude Code

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 commands/mort-lab/excel-mcp/prp-core-commit
Clone the repo
git clone --depth 1 https://github.com/mort-lab/excel-mcp

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 388 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.00000 $0.00388
Opus 5 $0.00000 $0.00194
Sonnet 5 $0.00000 $0.00078
Haiku 4.5 $0.00000 $0.00039

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

Security

Grade A, and why

prp-core-commit 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.

.claude/commands/prp-core/prp-core-commit.md · 56 lines

What it actually says

Create Git Commit

Create an atomic git commit with a properly formatted commit message following best practices for the uncommited changes or these specific files if specified.

Specific files (skip if not specified):

  • File 1: $1
  • File 2: $2
  • File 3: $3
  • File 4: $4
  • File 5: $5

Instructions

Commit Message Format:

  • Use conventional commits: <type>: <description>
  • Types: feat, fix, docs, style, refactor, test, chore
  • Present tense (e.g., "add", "fix", "update", not "added", "fixed", "updated")
  • 50 characters or less for the subject line
  • Lowercase subject line
  • No period at the end
  • Be specific and descriptive

Examples:

  • feat: add web search tool with structured logging
  • fix: resolve type errors in middleware
  • test: add unit tests for config module
  • docs: update CLAUDE.md with testing guidelines
  • refactor: simplify logging configuration
  • chore: update dependencies

Atomic Commits:

  • One logical change per commit
  • If you've made multiple unrelated changes, consider splitting into separate commits
  • Commit should be self-contained and not break the build

IMPORTANT

  • NEVER mention claude code, anthropic, co authored by or anything similar in the commit messages

Run

  1. Review changes: git diff HEAD
  2. Check status: git status
  3. Stage changes: git add -A
  4. Create commit: git commit -m "<type>: <description>"

Report

  • Output the commit message used
  • Confirm commit was successful with commit hash
  • List files that were committed
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 · 56 lines · 0 tokens per session scan A 90a97a5bd8cb

Subscribe to this mod's changes

prp-core-commit is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 388 tokens. 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.