EverOS is a Python library and local-first memory runtime that gives AI agents a portable memory layer across apps, devices, and workflows. It stores conversations, files, and agent activity as readable Markdown while maintaining local indexes for retrieval and reuse. The catalogue add-ons provide commands, skills, hooks, and settings for using EverOS with coding agents.
Borrowing it
Nothing to install: this file belongs to EverMind-AI/EverOS. 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/EverMind-AI/EverOS/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/EverMind-AI/EverOSWrote 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/evermind-ai/everos/commit)<a href="https://agentmods.dev/skills/evermind-ai/everos/commit"><img src="https://agentmods.dev/badge/skills/evermind-ai/everos/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/evermind-ai/everos/commit"><img src="https://agentmods.dev/badge/skills/evermind-ai/everos/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.00014 | $0.00472 |
| Opus 5.5 | $0.00006 | $0.00189 |
| Sonnet 5.5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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.
What it actually says
/commit
Create a well-formed commit following the Conventional Commits
standard. The format is enforced by gitlint in the commit-msg hook.
Steps
-
Run
git statusandgit diff(andgit diff --staged) to see what changed. -
Review recent history for style:
git log --oneline -10. -
Group the change into a single focused commit. If the working tree mixes unrelated changes, stage selectively (
git add -p/ specific paths) rather than committing everything at once. -
Write the message in Conventional Commits form:
<type>[(scope)][!]: <imperative summary, ≤72 chars> <optional body: what & why, wrapped at 72> <optional footer: BREAKING CHANGE: …, Refs: #123> -
Never use
--no-verify. If pre-commit hooks fail, fix the cause and re-commit. -
Do not commit secrets, generated artifacts, or work-in-progress directly to the protected
mainbranch.
Types
| Type | Use for |
|---|---|
feat |
new feature |
fix |
bug fix |
refactor |
behavior-preserving restructure |
test |
add / update tests |
docs |
documentation |
style |
formatting only |
perf |
performance |
chore |
config / build / tooling |
build |
build system or dependencies |
ci |
CI configuration |
revert |
revert a previous commit |
Notes
- No emoji — the title must start with the
type. - One logical change per commit; keep the history bisectable.
- The summary is imperative mood: "add", not "added" / "adds".
scopeis optional:fix(search): …. A!before the colon (or aBREAKING CHANGE:footer) marks a breaking change.
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 · 14 tokens per session scan A 86365f623471
commit is a skill published in the GitHub repository EverMind-AI/EverOS (13,824 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 472 once invoked, about $0.0001 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 |
|---|---|---|---|---|---|---|---|
| commitEverMind-AI/EverOS | Skill | 14k | yesterday | Apache-2.0 | A | 14 | Claude Code |
| githubMemTensor/memmy-agent | Skill | 2.2k | today | MIT | A | 44 | Claude Code, Codex |
| computer-historyMemTensor/memmy-agent | Skill | 2.2k | today | MIT | A | 42 | Claude Code, Codex |
| docxMemTensor/memmy-agent | Skill | 2.2k | today | MIT | A | 40 | Claude Code, Codex |
| update-setupMemTensor/memmy-agent | Skill | 2.2k | today | MIT | A | 0 | Claude Code, Codex |
| skill-creatorMemTensor/memmy-agent | Skill | 2.2k | today | MIT | A | 28 | Claude Code, Codex |
| memmy-memoryMemTensor/memmy-agent | Skill | 2.2k | today | MIT | A | 34 | Claude Code, Codex |