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 agentmods add skills/kltsv/ai-vendor-agnostic-setup/commitnpx skills add kltsv/ai-vendor-agnostic-setup --skill commitgit clone --depth 1 https://github.com/kltsv/ai-vendor-agnostic-setupWrote 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/kltsv/ai-vendor-agnostic-setup/commit)<a href="https://agentmods.dev/skills/kltsv/ai-vendor-agnostic-setup/commit"><img src="https://agentmods.dev/badge/skills/kltsv/ai-vendor-agnostic-setup/commit.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00297 |
| Opus 5 | $0.00016 | $0.00148 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 4d 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.
What it actually says
Commit
This skill is the example skill for the harness: it is authored once in
.agents/skills/commit/ and mirrored verbatim into every vendor's skills
directory by .agents/setup.py. Editing it here updates it everywhere.
When
Commit when a coherent unit of work is finished and in a known-good state — a working feature, a self-contained refactor, a doc update. Do not commit a half-written or broken tree. Prefer several small logical commits over one large dump.
How
git add <paths for this logical chunk>
git commit -m "<imperative summary>"
- Scope each commit to one logical change; stage explicit paths rather than
git add -Awhen a working tree holds unrelated edits. - Write the message in the imperative mood ("add", "fix", "rename"), present tense, no trailing period in the summary line.
- Generated mirrors (
.claude/,.codex/,CLAUDE.md) are gitignored and will not be staged — never commit them.
Rules
- One commit per logical chunk.
- Never commit a broken or half-finished tree.
- Don't push unless asked.
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.
- 4d ago First seen · 38 lines · 33 tokens per session scan A 698c6e1df72c
commit is a skill published in the GitHub repository kltsv/ai-vendor-agnostic-setup (5 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 297 once invoked, about $0.0002 per session on Opus 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
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…
trellis-finish-work
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
commit
Create a signed git commit following Conventional Commits, after running /pre-commit and /changelog when appropriate.
commit
Read this skill before making git commits.