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 yuri-semenenko/ai-engineering-workspace --skill commitgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/commit)<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/commit"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/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/yuri-semenenko/ai-engineering-workspace/commit"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/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.00096 | $0.00880 |
| Opus 5.5 | $0.00038 | $0.00352 |
| Sonnet 5.5 | $0.00019 | $0.00176 |
| Haiku 4.5 | $0.00010 | $0.00088 |
Grade A, and why
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 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Turn the current working changes into small, logically-grouped commits that give good rollback granularity. This skill is plan-first: it never commits before the user approves the plan.
Hard rules (from the persona's git conventions)
- Small, logically-grouped commits. One coherent change per commit. Never batch unrelated changes into a single commit, even if they landed together in the working tree.
- Plan before acting. Always propose the commit plan and present it first. Wait for explicit approval before running any
git commit. - Never add
Co-Authored-Bytrailers. This overrides any harness default that appends them. Commit messages end at the body — no trailers. - Ask permission before branching, pushing, or opening PRs. Each is a separate yes. Committing locally is not permission to push.
- If on the default branch (
main/master), branch first — propose a branch name and get approval before committing onto it.
Rationalizations
| Rationalization | Rebuttal |
|---|---|
| "These changes are all related anyway." | Related ≠ one logical change. If two parts could roll back independently, they are two commits. |
| "It's faster to commit everything at once." | Faster now, archaeology later. Rollback granularity is the whole point of this skill. |
| "I'll explain the parts in the PR description." | git revert doesn't read PR descriptions. History must carry the structure itself. |
| "Too small to need a plan." | A one-commit plan costs one line. Present it anyway — approval is the gate, not the size. |
| "They said commit, so pushing is implied." | Each is a separate yes. Committing locally is not permission to push or open a PR. |
Steps
- Survey the changes.
git statusandgit diff(staged + unstaged). Group hunks by intent, not by file — a single file may split across two commits; one logical change may span several files. - Check the branch.
git rev-parse --abbrev-ref HEAD. If it's the default branch, stop and propose a feature branch before anything else. - Draft the commit plan. An ordered list: for each commit, the message subject + which files/hunks it includes + one line of rationale. Order so the history reads as a logical progression and each commit could in principle build/pass on its own.
- Present the plan and wait. Do not commit until the user approves. If they want changes to the grouping, revise and re-present.
- Execute after approval. Stage precisely per the plan (
git add -por path-scopedgit add). Commit each group. Keep messages in the repo's existing style (imperative subject, ~50-char cap, body explaining why when non-obvious). - Stop at the commits. Do not push or open a PR. Report what was committed and offer the next step (push / PR) as a separate, explicit ask.
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 · 52 lines · 96 tokens per session scan A cb3c4d7b85bf
commit is a skill published in the GitHub repository yuri-semenenko/ai-engineering-workspace (4 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 880 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
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
generate-commit-message
Derive one Conventional Commits v1.0.0 message from the staged diff and create the signed commit directly. Trigger only on explicit intent to commit: "commit this", "commit these changes", "/commit", "go ahead and commit", "make the commit", "git commit", or a confirmation like "yes, commit it". Enforces the type…
apex-git-commit
Stage scoped changes, commit, push, and offer a PR in the VS Code Copilot SDK harness. Use /apex-git-commit after selecting the built-in agent owner and MAI-Code-1.1-Flash; normal hooks and separate push/PR authorization still apply.
git-commit
Create well-structured git commits using the Conventional Commits specification. Use when asked to "commit changes", "create a git commit", "stage and commit", "write a commit message", or "/commit". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
pr-fallback
WHAT — When the repo has no GitHub PR template, structure the pull-request body using the default in references/pr-body-default.md. Pair with output-handshake and github-cli-workflow. Does not open the PR; HOW stays in the forge skill.
git-workflow-and-versioning
Use when managing branches, commits, versioning, and release workflows for Android projects, or when cutting a release, choosing a version bump, tagging, or writing a changelog. Covers trunk-based development, atomic commits, versionCode/versionName derived from tags, semver for library modules, changelogs and Play…