Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.
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/davila7/claude-with-skills/commit-messagenpx skills add davila7/claude-with-skills --skill commit-messagegit clone --depth 1 https://github.com/davila7/claude-with-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/davila7/claude-with-skills/commit-message)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/commit-message"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/commit-message.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.00038 | $0.00471 |
| Opus 5 | $0.00019 | $0.00235 |
| Sonnet 5 | $0.00008 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
commit-message 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 5d 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
Instructions
-
Run
git diff --stagedto see exactly what is staged for the next commit. -
Run
git status --shortto understand the full scope of changes (staged and unstaged) and identify the files involved. -
If nothing is staged, tell the user there is nothing staged and suggest they run
git addfirst. Stop here. -
Choose the correct Conventional Commits type based on the diff:
feat: a new feature or capability visible to users or callersfix: a bug fixdocs: documentation changes onlystyle: formatting, whitespace, missing semicolons — no logic changerefactor: code restructuring with no behavior change and no new featuretest: adding or correcting testschore: build system, dependency updates, tooling, CI config
-
Determine the scope from the changed files. The scope is optional but useful when the change is clearly isolated to one module, package, or layer (for example,
api,auth,db,cli). Omit it if the change is broad. -
Write the subject line:
- Format:
type(scope): descriptionortype: descriptionif no scope - Imperative mood: "add", "fix", "remove" — not "added", "fixes", "removing"
- Maximum 72 characters
- No period at the end
- Format:
-
If the diff is non-trivial (more than one logical change, or a change whose motivation is not obvious from the code), add a body:
- Blank line after the subject
- Bullet points explaining why the change was made, not what it does (the diff already shows what)
- Keep each bullet under 72 characters
-
Output only the commit message text. No surrounding explanation, no markdown code block wrapping.
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.
- 5d ago First seen · 39 lines · 38 tokens per session scan A 76cbb015f980
commit-message is a skill published in the GitHub repository davila7/claude-with-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 471 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
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…