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/selorahomes/ha-selora-ai/commitnpx skills add SeloraHomes/ha-selora-ai --skill commitgit 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.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.00012 | $0.00628 |
| Opus 5 | $0.00006 | $0.00314 |
| Sonnet 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 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.
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.
- 4d 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 (82 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 628 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-30.
Other skills, from other repositories
bat-story-eval
Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.
contrib-pr-review
Review a contribution PR for safety, quality, and readiness. Checks for security concerns, test coverage, size appropriateness, and intent alignment. Use when reviewing external contributions.
bat-adhoc
Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective. Use when testing PRs, detecting regressions, or verifying tool changes end-to-end with Claude/Gemini CLIs.
contributors-update
Find merged PR authors missing from README and update the contributors list after approval.
issue-to-pr-resolver
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…
my-pr-checker
Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".