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 cdskill/qalma --skill git-commitgit clone --depth 1 https://github.com/cdskill/qalmaWrote 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/cdskill/qalma/git-commit)<a href="https://agentmods.dev/skills/cdskill/qalma/git-commit"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/git-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/cdskill/qalma/git-commit"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/git-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.00046 | $0.00943 |
| Opus 5.5 | $0.00018 | $0.00377 |
| Sonnet 5.5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
git-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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Create a focused conventional commit from the changes that are already staged.
Every commit in this repository MUST carry a type(scope): description header —
a commit without a scope is invalid here.
Workflow
- Run
git status --shortto understand staged, unstaged, and untracked files. - Run
git diff --stagedand analyze only staged changes. - If nothing is staged, stop and ask the user to stage changes first.
- Pick the
typeand a requiredscopefrom the tables below, based on the staged paths. If the diff legitimately spans several scopes, either split it into separate commits or use the broadest accurate scope (e.g.repo). - Generate a conventional commit message that reflects the staged diff.
- Validate before committing: the subject line MUST match
^(feat|fix|docs|style|refactor|perf|test|build|ci|chore)\([a-z0-9-]+\)!?: .+. If it does not (e.g. the scope is missing), fix the message — never commit without a scope. - Create the commit with
git commitusing the validated multi-line message. - Report the commit hash and message summary.
Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer]
The (<scope>) segment is not optional in this repository.
Types
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style or formatting changesrefactor: Code restructuring without behavior changesperf: Performance improvementtest: Adding or modifying testsbuild: Build system, dependencies, or packagingci: CI/CD pipeline changeschore: Maintenance tasks
Scopes (required — pick the most specific match)
| Scope | Use for changes under… |
|---|---|
editor |
libs/editor — the @qalma/editor library |
docs |
apps/docs / apps/docs-e2e — the documentation site |
sandbox |
apps/sandbox / apps/sandbox-e2e — the demo app |
bench |
bench/** — benchmarks (e.g. bundle-size) |
infra |
infra/** — Terraform/OpenTofu, hosting, CDN |
skills |
.agents/skills / .claude/skills |
agents |
.agents agent configuration (non-skill) |
release |
Version bumps and release publishing |
repo |
Repo-wide tooling, root config, or genuinely cross-cutting changes |
What ships with it
1 file 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 · 99 lines · 46 tokens per session scan A 1bab41cf1543
git-commit is a skill published in the GitHub repository cdskill/qalma (10 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 943 once invoked, about $0.0002 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
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
commit
Create git commits in the Unovis repo that pass its commitlint rules. Unovis uses a CUSTOM commit format (Type | Scope | Subscope: Sentence-case subject), NOT Conventional Commits, so feat:/fix: will be rejected by the commit-msg hook. Use this whenever staging and committing changes, writing or rewriting a commit…
open-pr
Open a pull request for the Unovis repo with the project's conventions — correct branch off main, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.
group-chat-checkin
Coordinate parallel sessions for discussion, task execution, and git commits.
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.