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/mozi-developmentnpx skills add spytensor/openmozi --skill mozi-developmentgit 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.00037 | $0.01636 |
| Opus 5 | $0.00018 | $0.00818 |
| Sonnet 5 | $0.00007 | $0.00327 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade A, and why
mozi-development 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on MOZI
Load this before adding or changing anything in this codebase. Its job is to stop you rediscovering the architecture by grep every time — and, more importantly, to stop you drawing the wrong map, which is the failure this codebase keeps repeating.
The companion artifact is docs/atlas/MOZI-架构全景.html — a module-by-module
map of this runtime: design, implementation, third-party vs custom, call paths,
wiring verdicts backed by non-test callers, examples and known traps. Read
the section for the layer you are touching before designing anything. Its code
excerpts are extracted from the tree by anchor, not transcribed, so they cannot
silently drift.
When you finish a change, run python3 docs/atlas/staleness.py. It reports
which atlas modules your diff invalidated — usually a handful — so the map is
updated by targeted rescans rather than by repeating the full sweep, which is
what let the previous atlas rot 151 commits behind. If it reports files that
belong to no module, you have either added a subsystem the map does not know
about or found a coverage gap; either way it needs an entry.
Why a scan of the code lies to you
Three failure modes, all with real incidents behind them. Assume all three are present until you have checked.
- Code exists, nothing calls it. Vector memory sat installed and dead for
four months.
memory_summarieshad a UI reading a table nothing wrote. The whole telemetry pipeline had dashboards and replay tooling while its three writers had zero callers. A grep that finds a function proves nothing about whether it runs. - Documentation describes intent, not behaviour. Files claim capabilities
the runtime never registered.
docs/andCLAUDE.mdhave both been wrong about live call paths. Trust the call graph over any prose, including this file. - A second implementation quietly wins. Two build-script allowlists existed; only one was read, so a dependency's install step never ran and the conflict also swallowed the warning. When behaviour contradicts configuration, look for the other implementation before concluding the config is broken.
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 · 139 lines · 37 tokens per session scan A b2a11d8aba2b
mozi-development is a skill published in the GitHub repository spytensor/openmozi (210 stars, last pushed 26d ago), licensed MIT. It adds 37 tokens to every session and 1,636 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
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…
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.
skill-creator
Create or update Memoh workspace skills under /data/skills, including SKILL.md, scripts, references, assets, and validation. Use when the user asks to create, scaffold, revise, audit, or explain a workspace skill.
hooks-setup
Configure Memoh hooks in /data/.memoh/hooks.json, including events, matchers, command/tool actions, decisions, onerror behavior, appendcontext, and validation. Use when the user asks to inspect, create, update, debug, or explain workspace hooks.
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.