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 yarlson/yarstack --skill phase-commitgit clone --depth 1 https://github.com/yarlson/yarstackWrote 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/yarlson/yarstack/phase-commit)<a href="https://agentmods.dev/skills/yarlson/yarstack/phase-commit"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/phase-commit/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/yarlson/yarstack/phase-commit"><img src="https://agentmods.dev/badge/skills/yarlson/yarstack/phase-commit.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.00036 | $0.00358 |
| Opus 5.5 | $0.00014 | $0.00143 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
phase-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 7d 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.
What it actually says
Phase Commit
Create one isolated local commit without changing history or external state.
Workflow
- Confirm required repository checks and applicable validation and review cover the exact intended content.
- Inspect status, staged and unstaged changes, and relevant untracked files; preserve all unrelated user work.
- Stop when scope is ambiguous or includes sensitive, unexpectedly generated, or otherwise unsafe paths.
- Stage only explicit paths with
git add -- <paths>; never use broad staging commands or globs. - Review the staged path list and diff against the requested unit. If the unit mixes a behavior-preserving restructuring with a behavior change, say so and offer two commits; commit them together only if the user keeps one.
- Draft the commit subject and body using repository conventions. Without a convention, write a short imperative subject and a body that states the problem, the change, and why. Then use
text-improvewithout changing technical meaning. - Commit without bypassing hooks or changing signing policy.
- Verify the created commit with
git show --stat HEADand the remaining worktree withgit status --short.
Do not amend, rewrite history, push, create branches or pull requests, manage CI, tag, release, or include unrelated changes.
When a hook only reformats the staged paths, review its changes, stage those same paths, and commit once more. On any other hook or commit failure, stop and report the blocker without claiming completion.
Finish only after verifying the created commit, then report its hash and concise summary.
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.
- 7d ago Changed 0e8aaf4b6c04
- 1mo ago First seen · 26 lines · 36 tokens per session scan A 73189c72ead4
phase-commit is a skill published in the GitHub repository yarlson/yarstack (3 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 358 once invoked, about $0.0001 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-31.
Other skills, from other repositories
owndiff-pre-commit
Audit OwnDiff changes before committing or releasing by checking scope, generated artifacts, private data, documentation accuracy, version consistency, structured files, tests, and the OwnDiff ownership gate. Use when a user asks to verify, clean up, prepare, commit, publish, or release changes in the OwnDiff…
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.
gentle-ai-work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.