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 mystilleef/spae-framework --skill auto-commitgit clone --depth 1 https://github.com/mystilleef/spae-frameworkWrote 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/mystilleef/spae-framework/auto-commit)<a href="https://agentmods.dev/skills/mystilleef/spae-framework/auto-commit"><img src="https://agentmods.dev/badge/skills/mystilleef/spae-framework/auto-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/mystilleef/spae-framework/auto-commit"><img src="https://agentmods.dev/badge/skills/mystilleef/spae-framework/auto-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.00019 | $0.01199 |
| Opus 5.5 | $0.00008 | $0.00480 |
| Sonnet 5.5 | $0.00004 | $0.00240 |
| Haiku 4.5 | $0.00002 | $0.00120 |
Grade C, and why
auto-commit scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- prettier-ignore-start --> How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-commit agent
When to use
- Invoke for any repository with pending changes that should land as atomic commits.
- Execute immediately upon invocation. Never wait for user input or
confirmation before
git status.
Goal
- Analyze repository changes, form safe atomic groups, block secrets, stage targeted files, and create conventional commits in the current project.
- Commit all eligible current-project changes as separate, logical, atomic commits.
- Leave the working tree clean unless safety checks or git errors block completion.
Input
Determine input from the current repository state:
- Tracked,
untracked, staged,unstaged, renamed, deleted, and ignored changes reported by git. - Atomic grouping heuristics from
references/atomic-git-staging.md. - Commit message rules from
references/conventional-commit.md.
Workflow
- GATE—Run
git --no-pager status --porcelain=v2 --branch. Halt on no changes or git error. - ORIENT—Goal: commit all eligible changes as atomic commits. Scope: current project. No changes outside git state.
- PLAN—Group files into logical commits. Isolate
.gitignorechanges. Apply fast path for a single unstaged file. - ACT (repeat steps 4–6 per group until no eligible changes
remain)—
- Scan candidate paths and content for secrets (pre-stage).
- Run
git --no-pager diff --no-ext-diff --stat --minimal --patience --histogram --find-renames --summary --no-color -U10 <file_group>. - Run
git --no-pager add <file1> <file2> .... - Scan staged diff for secrets (pre-commit).
- Generate conventional commit message.
- VERIFY—Confirm staged diff matches intent and all secret checks pass. On failure: unstage, halt, report.
- PERSIST—Run
git --no-pager commit -m "<message>". Confirm commit success. - REPORT—Emit the result following the result directives and using the result template.
Directives
- Atomic Grouping: Commit files together only when they must change together, such as implementation plus matching tests.
- Gitignore Isolation: Commit
.gitignorechanges separately. - Sensitive Path Rules: Hard-block
.env*except.env.example,*.key,*.pem,*.p12,*.pfx,*_rsa,*_dsa,id_*,secrets.*,credentials.*,.aws/,.ssh/, and.gnupg/.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 142 lines · 19 tokens per session scan C 92cd68752669
auto-commit is a skill published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,199 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
git-workflow-and-versioning
Git workflow and versioning practices. Use when committing, branching, resolving conflicts, organizing work across multiple parallel streams, cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
commit-pr
A command for the workflow of committing code, sending it to a remote Git repository, and opening or updating a pull request. A pull request is a proposed change for review and merging.
batonq-pr-runner
Implements a batonq task end-to-end and opens a pull request. Adds git discipline, branch naming, conventional-commit enforcement, and PR-body conventions on top of batonq-worker. Use when a task explicitly requires a PR (not a direct commit to main) — e.g., tasks running in fire-and-forget mode against repos with…
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.