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/advayroy/slate-skills/slate-commitnpx skills add AdvayRoy/slate-skills --skill slate-commitgit clone --depth 1 https://github.com/AdvayRoy/slate-skillsWrote 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/advayroy/slate-skills/slate-commit)<a href="https://agentmods.dev/skills/advayroy/slate-skills/slate-commit"><img src="https://agentmods.dev/badge/skills/advayroy/slate-skills/slate-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.00024 | $0.00283 |
| Opus 5 | $0.00012 | $0.00142 |
| Sonnet 5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
slate-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
slate-commit
Write clean commit messages. Short subject. Body only when needed.
Subject
<type>(<scope>): <imperative summary>
Types:
featfixrefactorperfdocstestchorebuildcistylerevert
Rules
- Imperative mood:
add,fix,remove, notaddedoradds. - Prefer <=50 chars. Hard cap 72 chars.
- No trailing period.
- Body only for non-obvious why, breaking changes, migrations, security fixes, reverts, linked issues.
- Never include AI attribution unless project policy requires it.
- Output commit message in one code block.
Examples
fix(auth): reject expired JWTs
feat(api)!: rename /v1/orders to /v1/checkout
BREAKING CHANGE: clients must migrate before 2026-06-01.
Old route returns 410 after cutoff.
Boundary
Only generate commit message. Do not stage, commit, amend, or push.
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.
- 4d ago First seen · 58 lines · 24 tokens per session scan A bd75c09a3392
slate-commit is a skill published in the GitHub repository AdvayRoy/slate-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 283 once invoked, about $0.0001 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…
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…
commit
Read this skill before making git commits.
et-git
ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.
commit
Smart commit: bump version, find related issues, commit with Co-authored-by, push. Use when the user says 'commit' or wants to finalize changes.
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.