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/spytensor/openmozi/commitnpx skills add spytensor/openmozi --skill commitgit clone --depth 1 https://github.com/spytensor/openmoziWhat 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.00035 | $0.00521 |
| Opus 5 | $0.00017 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 yesterday.
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
Smart Commit
When the user asks to commit, execute ALL of these steps:
Step 1: Analyze Changes
git status
git diff --stat
git diff
git log --oneline -5
Understand what was changed and why.
Step 2: Determine Version Bump
Read package.json to get the current version. Determine the bump type based on changes:
- patch (x.y.Z): bug fixes, minor tweaks
- minor (x.Y.0): new features, new commands, new modules
- major (X.0.0): breaking changes
Update the "version" field in package.json.
Step 3: Find Related Issues
Check if there are open GitHub issues related to the changes:
gh issue list --state open --limit 20
Match the changes against issue titles/descriptions. If a related issue is found, reference it in the commit message as (#N) and close it after pushing.
If $ARGUMENTS contains an issue number, use that directly.
Step 4: Build & Test
pnpm build
pnpm test
If either fails, fix the issues before committing. Do NOT commit broken code.
Step 5: Commit
Stage the changed files (be specific, avoid git add -A for safety):
git add <specific files>
git commit -m "<type>: <description> (#<issue>)
Co-authored-by: Mozi <[email protected]>"
Commit type: feat: for features, fix: for bugs, refactor: for refactors, chore: for config/deps.
Step 6: Push
git push origin main
Step 7: Close Related Issues
If a related issue was found:
gh issue close <N> --comment "Implemented in <commit-hash> (v<new-version>)."
Step 8: Report
Print a summary:
- Version: old -> new
- Commit: hash
- Files changed: count
- Issue closed: #N (if any)
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.
- yesterday First seen · 87 lines · 35 tokens per session scan A 3f590ee1b970
commit is a skill published in the GitHub repository spytensor/openmozi (192 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 521 once invoked, about $0.0002 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
lobu-operator
Contribute safely to the Lobu monorepo: worktrees, package rules, red-to-green fixes, validation gates, SDK-first operations, PRs, and rollout checks.
company-agent-infrastructure
Use when designing or building internal/company AI agents that need shared context across company systems, durable organizational memory across sessions or agents, user-scoped permissions, approvals, audit, or governed actions. Also use when deciding whether ordinary MCP tools, RAG, or local agent memory are enough…
lobu-builder
Use when working inside a Lobu project generated by @lobu/cli or any repository centered on lobu.config.ts, AGENTS.md, agent prompt files, local skills, and evals. This skill helps a coding agent inspect the right files, make Lobu-native changes, keep the stack runnable, and validate semantics with chat tests and…
crm-ops
How to operate the Lobu funnel CRM — create and enrich leads, log interactions, advance funnel stages, open and update pilots, and produce the weekly digest. Use whenever the task touches the pipeline.
deliveroo-order
Turn collected lunch orders into a clean per-person order list for a human to place on Deliveroo. Use in step 2 of the lunch run, after orders are collected. The live menu is fetched automatically by the lobu-team-lunch-finalize reaction (via the Owletto Chrome extension) — this skill never places an order or touches…
lobu
Use Lobu MCP for shared, permission-aware company context, durable organizational memory, and governed actions. Trigger when the user asks what the organization knows, needs context from connected company systems, wants to preserve a durable fact or decision, or needs to discover and use Lobu SDK capabilities.