Borrowing it
Nothing to install: this file belongs to SeloraHomes/ha-selora-ai. 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/SeloraHomes/ha-selora-ai/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/SeloraHomes/ha-selora-aiWrote 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/selorahomes/ha-selora-ai/commit)<a href="https://agentmods.dev/skills/selorahomes/ha-selora-ai/commit"><img src="https://agentmods.dev/badge/skills/selorahomes/ha-selora-ai/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/selorahomes/ha-selora-ai/commit"><img src="https://agentmods.dev/badge/skills/selorahomes/ha-selora-ai/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.00012 | $0.00628 |
| Opus 5.5 | $0.00005 | $0.00251 |
| Sonnet 5.5 | $0.00002 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Create a git commit for staged and unstaged changes.
Commit message format
This project uses commitlint with @commitlint/config-conventional, enforced by a lefthook commit-msg hook.
Rules:
- Format:
<type>: <subject>(no scope required) - Subject: max 50 characters total (including
type:prefix), lowercase, no trailing period - Body (optional): wrap at 72 characters, separated from subject by a blank line
Choosing the right commit type
This project uses semantic-release. Some types trigger a release (new version published to users), others do not. Choose carefully — a wrong type means an unnecessary release.
Release-triggering types — only use when the change is meaningful to end users:
feat:→ minor release — a new user-facing featurefix:→ patch release — a bug fix that affects user behaviorperf:→ patch release — a performance improvement users would noticerefactor:→ patch release — use only if it changes observable behavior; otherwise usechore:revert:→ patch release — reverting a user-facing change
Non-release types — use for everything else:
chore:→ no release — tooling, CI, dependencies, config, internal cleanupdocs:→ no release — documentation changesstyle:→ no release — formatting, whitespace, linting fixestest:→ no release — adding or fixing testsci:→ no release — CI/CD pipeline changesbuild:→ no release — build system changes
Rule of thumb: if the change doesn't affect what end users experience when running the integration, it should NOT trigger a release. Use chore:, docs:, style:, test:, ci:, or build: instead.
Examples:
- Fixing lefthook config →
chore:(notfix:— this is internal tooling) - Updating internal doc references →
docs:(notfix:) - Optimizing CI/hook parallelism →
chore:(notperf:— users don't see this) - Fixing a bug in device discovery →
fix:(users are affected) - Adding a new sensor entity →
feat:(users get new functionality)
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 · 55 lines · 12 tokens per session scan A 43709d8a4bda
commit is a skill published in the GitHub repository SeloraHomes/ha-selora-ai (92 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 628 once invoked, about $0.0000 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.
commit compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| commitSeloraHomes/ha-selora-ai | Skill | 92 | yesterday | MIT | A | 12 | Claude Code |
| my-pr-checkerhomeassistant-ai/ha-mcp | Skill | 5.4k | yesterday | MIT | A | 75 | Claude Code |
| contributors-updatehomeassistant-ai/ha-mcp | Skill | 5.4k | yesterday | MIT | A | 17 | Claude Code |
| issue-to-pr-resolverhomeassistant-ai/ha-mcp | Skill | 5.4k | yesterday | MIT | A | 85 | Claude Code |
| wthomeassistant-ai/ha-mcp | Skill | 5.4k | yesterday | MIT | A | 18 | Claude Code |
| create-prprisma/orm | Skill | 48k | yesterday | Apache-2.0 | A | 48 | Claude Code, Codex |
| git-commitThinkInAIXYZ/deepchat | Skill | 6.4k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |