Borrowing it
Nothing to install: this file belongs to bablsoft/accessflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bablsoft/accessflow/main/.claude/skills/commit-sequence/SKILL.mdgit clone --depth 1 https://github.com/bablsoft/accessflowWrote 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/bablsoft/accessflow/commit-sequence)<a href="https://agentmods.dev/skills/bablsoft/accessflow/commit-sequence"><img src="https://agentmods.dev/badge/skills/bablsoft/accessflow/commit-sequence/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/bablsoft/accessflow/commit-sequence"><img src="https://agentmods.dev/badge/skills/bablsoft/accessflow/commit-sequence.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.00096 | $0.01162 |
| Opus 5.5 | $0.00038 | $0.00465 |
| Sonnet 5.5 | $0.00019 | $0.00232 |
| Haiku 4.5 | $0.00010 | $0.00116 |
Grade A, and why
commit-sequence 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commit-sequence
When to use
A working tree with several unrelated or separable changes. If everything is one change, just commit it — this skill exists to avoid the 40-file "misc" commit nobody can review.
Procedure
1. Read the tree
git status --short
git diff --stat
git diff --cached --stat
Note anything untracked that you did not create — never sweep those in. Ask, or leave them.
2. Propose groups
Present a numbered list: group name, conventional-commit subject, and the files. Then stop and let the user adjust before anything is staged.
3. Group by change, not by directory
AccessFlow's real logical units cut across the tree:
| Unit | Files that belong together |
|---|---|
| A backend feature | the module's api/ + internal/ + its tests + its migration (+ .sql.conf) + messages.properties + the six locales |
| An engine change | engines/<id>/** and connectors/<id>/connector.json — never split: a version bump without the re-pinned SHA fails CI and leaves the catalog pointing at a jar whose hash does not match |
| A frontend feature | src/api/<domain>.ts + the page/components + en.json + the six locales + e2e/tests/<flow>.spec.ts (+ the regenerated help-corpus/ when it touches en.json, Sidebar.tsx or reviewHubTabs.ts — the corpus derives its menu vocabulary from those, #925) |
| A validation change | the backend DTO constraint and the mirroring Form.Item rule — the parity rule makes these one commit by definition |
| A website change | website/**.html + sitemap.xml + the regenerated help-corpus/ (+ frontend/src/config/docs.ts when anchors moved) |
| A config knob | the *Properties record + application.yml + the docs/09-deployment.md row |
4. Never split these
- An engine
pom.xmlversion bump from itsconnectors/<id>/connector.jsonpin. - A migration from its
.sql.confsidecar. - An i18n key from its six translations.
- A backend constraint from its frontend rule.
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 Changed 3425be0e2653
- 1mo ago Changed ca42a0107c60
- 2mo ago First seen · 100 lines · 96 tokens per session scan A a4fc61ed20f4
commit-sequence is a skill published in the GitHub repository bablsoft/accessflow (11 stars, last pushed today), licensed Apache-2.0. It adds 96 tokens to every session and 1,162 once invoked, about $0.0004 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
automotive-hooks
Pre-commit, pre-push, post-commit, and post-deploy Git hooks for automotive ASPICE compliance. 24 hook scripts across 5 lifecycle stages.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.