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 skills add J-Pster/Psters_AI_Workflow --skill commit-changesgit 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/skills/j-pster/psters_ai_workflow/commit-changes)<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/commit-changes"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/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/skills/j-pster/psters_ai_workflow/commit-changes"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/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.00077 | $0.01042 |
| Opus 5.5 | $0.00031 | $0.00417 |
| Sonnet 5.5 | $0.00015 | $0.00208 |
| Haiku 4.5 | $0.00008 | $0.00104 |
Grade A, and why
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 1mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Changes Skill
Trigger conditions
Use this skill when the user:
- Pastes one or more issues (with
# TitleandIdentifier: TICKET-XXXlines) and wants to commit. - Says "commit with these tickets", "commit my changes for TICKET-727", "commit everything and tag by ticket", or similar.
- Runs the /pwf-commit-changes slash command with pasted content.
What to do
Follow the workflow in commands/commit-changes.md exactly.
Summary of phases
- Parse — extract
{ id: "TICKET-XXX", title: "..." }for each ticket from the pasted text. - Discover repos —
git -C <path> status --shortfor every workspace path; skip empty or non-git. Collect only the list of repos with changes (no diffs at orchestrator level). - Spawn one subagent per repo (all in parallel) — each subagent (generalPurpose, model: fast) reads
skills/commit-changes-repo-worker/SKILL.md, fetches per-file diffs itself, classifies each file to the best ticket, groups files by ticket, and makes multiple targeted commits (one per group). Reports back a JSON result with acommitsarray. - Summarize — parse JSON results from all subagents, print a results table (one row per commit), show total commit count.
Worker skill
Each per-repo subagent follows skills/commit-changes-repo-worker/SKILL.md.
The main agent passes these inputs to each worker:
REPO_PATH— absolute pathREPO_NAME— short nameTICKET_LIST— formatted list ofTICKET-XXX: title
The worker fetches its own per-file diffs — no diff text is passed from the orchestrator.
Key difference from single-commit approach
The worker never runs git add -A. Instead, for each ticket group it runs:
git -C <REPO_PATH> add -- <file1> <file2> ...
git -C <REPO_PATH> commit -m "<ticket-specific message>"
This produces clean, reviewable git history with one commit per ticket per repo.
Commit message rules (rules/commits.mdc — always enforced)
[TICKET-XXXX] <emoji> <type>(<scope>): <subject>
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.
- 1mo ago First seen · 81 lines · 77 tokens per session scan A f4a245d001b0
commit-changes is a skill published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 77 tokens to every session and 1,042 once invoked, about $0.0003 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 skills, from other repositories
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
stepwise-task-execution
Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a needrevision bounce.
incremental-commits
Commit boundaries and messages on a task branch. Use when deciding where to cut a commit or how to word one while implementing.
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.
git-expert
Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.