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.
npx agentmods add commands/mturac/everything-openai-codex/prp-commitgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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.
[](https://agentmods.dev/commands/mturac/everything-openai-codex/prp-commit)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/prp-commit"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/prp-commit.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00015 | $0.00803 |
| Opus 5 | $0.00008 | $0.00402 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
prp-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prp-commit — 100% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Commit
Adapted from PRPs-agentic-eng by Wirasm. Part of the PRP workflow series.
Input: $ARGUMENTS
Phase 1 — ASSESS
git status --short
If output is empty → stop: "Nothing to commit."
Show the user a summary of what's changed (added, modified, deleted, untracked).
Phase 2 — INTERPRET & STAGE
Interpret $ARGUMENTS to determine what to stage:
| Input | Interpretation | Git Command |
|---|---|---|
| (blank / empty) | Stage everything | git add -A |
staged |
Use whatever is already staged | (no git add) |
*.ts or *.py etc. |
Stage matching glob | git add '*.ts' |
except tests |
Stage all, then unstage tests | git add -A && git reset -- '**/*.test.*' '**/*.spec.*' '**/test_*' 2>/dev/null || true |
only new files |
Stage untracked files only | git ls-files --others --exclude-standard | grep . && git ls-files --others --exclude-standard | xargs git add |
the auth changes |
Interpret from status/diff — find auth-related files | git add <matched files> |
| Specific filenames | Stage those files | git add <files> |
For natural language inputs (like "the auth changes"), cross-reference the git status output and git diff to identify relevant files. Show the user which files you're staging and why.
git add <determined files>
After staging, verify:
git diff --cached --stat
If nothing staged, stop: "No files matched your description."
Phase 3 — COMMIT
Craft a single-line commit message in imperative mood:
{type}: {description}
Types:
feat— New feature or capabilityfix— Bug fixrefactor— Code restructuring without behavior changedocs— Documentation changestest— Adding or updating testschore— Build, config, dependenciesperf— Performance improvementci— CI/CD changes
Rules:
- Imperative mood ("add feature" not "added feature")
- Lowercase after the type prefix
- No period at the end
- Under 72 characters
- Describe WHAT changed, not HOW
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 · 113 lines · 15 tokens per session scan A b0714d5d50c8
prp-commit is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 12d ago), licensed MIT. It adds 15 tokens to every session and 803 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-09-03.
Other commands, from other repositories
todo-branch
Structured workflow to transform vague todos into implemented features. Works on current branch with single commit at completion.
todo-worktree
Structured workflow to transform vague todos into implemented features using git worktrees and VS Code handoff. Supports task isolation, resumption, and clean commit history.
commit
Create git commits aligned with task completion, maintaining clean version control synchronized with task progress.
sync
Synchronize task status with git commits, ensuring consistency between version control and task tracking.
standup
Review my git commits from the past workday and generate a standup summary.
commit
智能生成 Git 提交信息并提交.