A Git commit-writing guide that records the reasoning behind a change alongside its commit message. It defines commit types and structured notes for constraints, rejected options, confidence, risk, testing, and follow-up work.

Use it to write consistent feature, fix, refactor, test, documentation, configuration, and performance commits with an attached decision history.

It makes the decisions behind code changes easier to understand later. Validation rules help ensure commits use the expected format and include required decision details.

lore-commit — Skill for Claude Code and Codex by Insajin/autopus-adk

Install

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.

Any agent

npx skills add Insajin/autopus-adk --skill lore-commit

Clone the repo

git clone --depth 1 https://github.com/Insajin/autopus-adk

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/insajin/autopus-adk/lore-commit/github.svg)](https://agentmods.dev/skills/insajin/autopus-adk/lore-commit)

Your own site

<a href="https://agentmods.dev/skills/insajin/autopus-adk/lore-commit"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/lore-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/insajin/autopus-adk/lore-commit"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/lore-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 672 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00020	$0.00672
Opus 5.5	$0.00008	$0.00269
Sonnet 5.5	$0.00004	$0.00134
Haiku 4.5	$0.00002	$0.00067

Measured 2mo ago against content hash 5f3e4e07d4b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lore-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.

.omp/skills/lore-commit/SKILL.md · 93 lines

What it actually says