Borrowing it
Nothing to install: this file belongs to ashaychangwani/imprint. 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/ashaychangwani/imprint/main/.agents/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/ashaychangwani/imprintWrote 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/ashaychangwani/imprint/commit)<a href="https://agentmods.dev/skills/ashaychangwani/imprint/commit"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/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/ashaychangwani/imprint/commit"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00523 |
| Opus 5.5 | $0.00008 | $0.00209 |
| Sonnet 5.5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
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 2mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Skill
Create a well-formed conventional commit from the currently staged changes.
Step 1 — Check staged changes
Run git diff --cached --stat to see what's staged. If nothing is staged, tell the user and stop.
Run git diff --cached to read the actual diff.
Step 2 — Determine commit type
Pick the type based on the nature of the change:
| Type | When to use |
|---|---|
feat |
New user-facing feature or capability |
fix |
Bug fix |
refactor |
Code restructuring without behavior change |
perf |
Performance improvement |
test |
Adding or updating tests |
docs |
Documentation only |
ci |
CI/CD configuration |
chore |
Maintenance, dependencies, tooling |
build |
Build system or external dependency changes |
style |
Formatting, whitespace, linting (no logic) |
Step 3 — Determine scope
Pick a scope from the file paths changed. Established scopes in this repo:
cli, probe, backend, playbook, stealth-fetch, cron, notify, utils, types, replay-backend, mcp, record, redact, session-writer
If the change spans multiple areas, omit the scope. If it's a new area, derive the scope from the directory name.
Step 4 — Write the commit message
Format: <type>(<scope>): <subject>
Rules:
- Subject line: imperative mood, lowercase, no period, under 72 chars
- Body (optional): explain WHY, not WHAT. Wrap at 100 chars.
- Footer (optional):
BREAKING CHANGE: <description>if applicable
Step 5 — Show and confirm
Show the proposed commit message to the user. Ask if they want to proceed, edit, or cancel.
Step 6 — Execute
Run the commit using a heredoc:
git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"
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.
- 2mo ago First seen · 70 lines · 20 tokens per session scan A 32007546c0be
commit is a skill published in the GitHub repository ashaychangwani/imprint (24 stars, last pushed 15d ago), licensed MIT. It adds 20 tokens to every session and 523 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-30.
Other skills, from other repositories
datalad
Retrieve, version, and publish scientific datasets with DataLad and git-annex, and capture computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a…
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…
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.