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 skills add mowenxd/cli --skill mo-sharedgit clone --depth 1 https://github.com/mowenxd/cliWrote 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/mowenxd/cli/mo-shared)<a href="https://agentmods.dev/skills/mowenxd/cli/mo-shared"><img src="https://agentmods.dev/badge/skills/mowenxd/cli/mo-shared/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/mowenxd/cli/mo-shared"><img src="https://agentmods.dev/badge/skills/mowenxd/cli/mo-shared.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00050 | $0.01652 |
| Opus 5.5 | $0.00020 | $0.00661 |
| Sonnet 5.5 | $0.00010 | $0.00330 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
mo-shared 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mocli - 墨问 CLI 共享规则
本技能是墨问 CLI 技能库的前置技能，指导你如何通过 mocli 完成配置初始化、API Key配置、与 mocli 的交互响应解析、展示规则以及安全规则。
前置参考
通用执行流程
- 先判断用户意图对应的具体
mocli子命令；不要用搜索类命令替代更精确的列表类命令。 - 如果命令需要 UID，而用户给的是人名、昵称或备注名，优先使用
mo-remark查找 UID；未命中时再使用用户搜索或询问用户补充 UID。 - 执行
mocli后先读取顶层code、status、reason，确认成功后再解析reply。 - 展示列表类结果时，优先使用 reply 中的有序 ID 列表（如
note_ids、uids、events）；再到对应的 Map（如notes、users）取详情，避免直接遍历 Map 导致顺序错误。
配置初始化
首次使用，用户需提供墨问 API Key， 使用 mocli auth init --apik <api-key> 来完成初始化。
API Key 配置与管理
- 使用过程中，如果
mocli响应AUTH错误（用户可能在墨问平台重置了 API Key 或者 本地配置丢失），可提醒用户重新提供 API Key，使用mocli auth init --apik <api-key> [--force]来重新初始化或更换(--force) API Key。 - 可以使用
mocli auth info [--profile]查看当前的配置信息，使用--profile额外获取当前 API Key 对应的账户，在墨问平台上的 Profile 信息。
响应解析规则
code=0且status=OK表示成功；业务数据通常在reply中。meta.alerts表示重要提示，成功或失败时都可能出现；应优先关注，并按提示类型决定展示位置，例如 CLI 新版本提醒通常附在业务结果之后。status=FAIL或code!=0表示失败，应优先展示reason、msg和meta.hints中的可执行建议。reason=AUTH：提醒用户重新提供 API Key，并使用mocli auth init --apik <api-key> --force更新配置；不要输出旧 API Key。reason=VALIDATE：说明参数不合法，并根据当前 skill 的参数范围给出可选修正。reason=NETWORK：说明网络或代理失败；如果是在受限环境里执行，可提示需要网络/代理权限。reason=API且存在api_error.trace_id：展示trace_id便于反馈问题，但不要泄露认证信息。- 如果返回为空列表或空 Map，明确说明“没有找到符合条件的数据”，不要编造结果。
响应展示规则
总则：根据用户的要求，基于数据条目的数据多少，尽量清晰、明确、格式优美的展示给用户
细则：
- 避免数据枯燥，适当增加一些 emoji 来增加数据的趣味性
- 时间戳格式化为可读的时间
- Bool 值尽量用 emoji 展示
- 如果数据比较少，就尽量详细的展示信息给用户
- 如果数据比较多，可以通过表格/列表等形式，尽量清晰、明确、格式优美的展示给用户。表格的字段选择上：
- 首先根据用户的要求，选择出用户关心的字段
- 如果用户没有指定字段，就展示大多数数据条目都具备的字段，最大化利用展示空间，同时尽量避免某一列只有少数数据
- 展示
UserInfo.name时，如果客户端支持 Markdown 或 HTML 链接、且同一UserInfo的home_url非空，使用该链接包裹名称（如[name](home_url)）；否则只展示名称，不编造或输出空链接。 - 展示
NoteInfo.title时，如果客户端支持 Markdown 或 HTML 链接、且同一NoteInfo的url非空，使用该链接包裹标题（如[title](url)）；否则按原有标题规则展示，不编造或输出空链接。 - 以上细则如果与用户的要求不一致，以用户的要求为准
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +2 lines f459f31680d0
- 2mo ago First seen · 86 lines · 50 tokens per session scan A 5b763b5a05ec
mo-shared is a skill published in the GitHub repository mowenxd/cli (40 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,652 once invoked, about $0.0002 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.