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 commands/isaacsight/kernel/commitgit clone --depth 1 https://github.com/isaacsight/kernelWrote 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/commands/isaacsight/kernel/commit)<a href="https://agentmods.dev/commands/isaacsight/kernel/commit"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/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.1 | $0.00000 | $0.00113 |
| Opus 5 | $0.00000 | $0.00056 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00011 |
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 2d 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
Review the current git diff and generate a thoughtful commit.
Steps:
- Run
git diff --statto see what changed - Run
git diffto see the actual changes - Analyze the changes and generate a concise, conventional commit message
- Stage all changes:
git add -A - Commit with the generated message
- Ask if the user wants to push
Commit message format: type(scope): description
Types: feat, fix, refactor, style, docs, chore, perf, test
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.
- 2d ago First seen · 14 lines · 0 tokens per session scan A 32f616cd69f8
commit is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 113 tokens. 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-09-03.
Other commands, from other repositories
write-release
Generate a release announcement essay in Eddie's voice for id8labs.app.
commit-push-pr
You are executing the commit-push-pr workflow - the most frequently used inner-loop command.
pr
Commit all changes, push to remote, and create a pull request.
commit
../../foundation/agentinstructions/cursorcommands/commit.md.
rollback
You are helping safely rollback recent changes. Be careful and clear.
commit
Create a new commit message following best practices and patterns outlined inside the skill.