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/skill-authoringnpx skills add spytensor/openmozi --skill skill-authoringgit 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.00097 | $0.01280 |
| Opus 5 | $0.00048 | $0.00640 |
| Sonnet 5 | $0.00019 | $0.00256 |
| Haiku 4.5 | $0.00010 | $0.00128 |
Grade A, and why
skill-authoring 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 3d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill authoring and installation
This is MOZI's own runtime contract for skills. It is not the same as
Claude Code's — skill-creator in this catalog is Anthropic's asset and
describes .claude/ conventions and a claude -p eval loop that do not apply
here. Follow this skill for anything that has to end up installed in MOZI.
Installing a package the user handed over
A skill package is an archive. .skill is the standard format (it is a zip);
users also send plain .zip, and it is common for the archive to contain the
.skill next to unrelated files they used while building it.
Pass the archive straight to install_skill. Do not unpack it first.
install_skill { "source": "path", "source_path": "<absolute path to the archive>" }
- Uploaded files arrive with their absolute path in your turn context. Use that path verbatim.
source: "path"also accepts a directory containingSKILL.md, or theSKILL.mdfile itself.source: "bundled"is only for reinstalling a skill MOZI already ships. It is never the right choice for a user's package — it needsskill_id, and a user's skill has no bundled id.- Add
"overwrite": trueonly when replacing a skill of the same name.
The runtime unpacks the archive, finds SKILL.md (at the root, in a single
wrapper directory, or in a single nested .skill), copies it into the workspace
skill directory, and reloads the catalog. The result includes eligible and any
missing_bins / missing_env.
If it refuses, the message says why. Act on it rather than retrying:
| Message | What to do |
|---|---|
No SKILL.md found inside <file> |
Not a skill package. Look inside with shell_exec and tell the user what it actually contains. |
contains N skills |
Ask which one, then point source_path at that directory after unpacking. |
Workspace skill already exists |
Confirm with the user, then repeat with "overwrite": true. |
missing_bins / missing_env non-empty |
It installed but cannot run yet. Tell the user exactly which binary or key is missing. |
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.
- 3d ago First seen · 118 lines · 97 tokens per session scan A 41932ca73061
skill-authoring is a skill published in the GitHub repository spytensor/openmozi (210 stars, last pushed 26d ago), licensed MIT. It adds 97 tokens to every session and 1,280 once invoked, about $0.0005 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…
self-motivation-corruption-system
系统性压力，机制驱动，持续输出.