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.
git clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/pwf-commit-changes)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-commit-changes"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-commit-changes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-commit-changes"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-commit-changes.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01434 |
| Opus 5.5 | $0.00022 | $0.00574 |
| Sonnet 5.5 | $0.00011 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
pwf-commit-changes 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 5 — Create Structured Commits
Use this command to produce high-quality, ticket-aware commits after review, including multi-repo parallel commit organization when needed.
Each repo gets its own subagent that:
- Inspects every changed file individually
- Groups files by which ticket they relate to
- Makes multiple focused commits — one per ticket group (plus separate commits for unrelated changes)
All repos run in parallel.
Input
<commit_changes_input> #$ARGUMENTS </commit_changes_input>
If empty, ask:
"Paste the issue(s) or list the ticket number(s) (e.g. TICKET-727, TICKET-726), then I'll commit all uncommitted changes with organized, per-ticket commits."
Phase 1 — Parse Tickets
Extract every ticket identifier and its short title from the pasted text:
- Look for
Identifier: TICKET-XXXlines; the title is the# Headingabove it (or after the last------separator). - Build a list:
[{ id: "TICKET-727", title: "Move the BACK TO TABLE button to the right side" }, ...] - If no ticket is found, subagents will still commit with descriptive subjects but no
[TICKET-XXX]prefix.
Phase 2 — Discover Repos With Changes
For each workspace path (all paths from context — backend, frontend, *-lambda, etc.):
- Run:
git -C <path> status --short - Skip if not a git repo (exit code ≠ 0) or output is empty.
- Record the repo path and name for repos that have uncommitted changes.
Note: Do NOT collect diffs here. Each subagent will fetch its own per-file diffs in Step 2 of its workflow, allowing precise file-level ticket classification.
Build a list: [{ path, name }] of repos with uncommitted changes.
Phase 3 — Spawn One Subagent Per Repo (All in Parallel)
Skill reference: Read
skills/commit-changes-repo-worker/SKILL.mdonce before spawning subagents to understand the multi-commit worker contract.
For each repo with uncommitted changes, invoke one generalPurpose subagent (model: fast) using the Task tool. All invocations run simultaneously.
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.
- 2mo ago First seen · 144 lines · 54 tokens per session scan A 1b2cafb67cfc
pwf-commit-changes is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 54 tokens to every session and 1,434 once invoked, about $0.0002 per session on Opus 5.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.
Other commands, from other repositories
commit
A Git commit command that reviews your changes and creates a Conventional Commits message, a standard format for describing what a change does.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
commit
Create a git commit using the Haiku model.
orc
Parallel multi-agent orchestration for complex features.
parallel-task
Execute bulk modifications across codebase with parallel agents and safety guarantees.
commit
Create a focused git commit after running quality checks.