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/mowenxd/cli/mo-usernpx skills add mowenxd/cli --skill mo-usergit clone --depth 1 https://github.com/mowenxd/cliWhat 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.00029 | $0.03222 |
| Opus 5 | $0.00015 | $0.01611 |
| Sonnet 5 | $0.00006 | $0.00644 |
| Haiku 4.5 | $0.00003 | $0.00322 |
Grade A, and why
mo-user 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
前置约束
CRITICAL — 先阅读 共享规则,其中包含 mocli 初始化、认证、输出解析以及安全规则
mocli user - 墨问用户
mocli user info --uid [--note]
本命令用于获取指定墨问用户的信息。--uid 是必填参数;--note 通过额外返回用户主页上的少量笔记样本,帮助 Agent 总结用户画像。
使用时机
- 当用户明确要“查看用户信息/获取用户资料/查某个 UID 的用户详情”时使用本命令。
- 当用户已经提供 UID,并希望查看该用户的基础资料、关注数、粉丝数或笔记数量时使用本命令。
- 当用户希望了解该用户的创作领域、创作方向、热门作品、推出过哪些专栏/合集、是否有付费内容等画像信息时,加上
--note获取样本后再总结。 - 当用户明确查询某一个用户的资料或信息时,默认使用
--note;这样除基础资料外,还能更完整地描绘这个用户“是个什么样的创作者”。 - 如果用户只提供昵称、姓名或备注名,先按
mo-shared的通用流程解析 UID:优先使用mo-remark,未命中时再使用mocli user search或询问用户补充 UID。
可选参数:
--uid string:目标用户 UID(必填)。--note:包含用户主页少量笔记样本,用于辅助总结用户画像。CLI 默认不包含;Agent 在明确查询单个用户资料时默认带上。
使用示例
- 获取 UID 为
Qiz5hxiY5wr5L76fyd8Kv的用户信息/简介mocli user info --uid "Qiz5hxiY5wr5L76fyd8Kv" --note - 介绍下墨问「二爷」
mocli user info --uid "Qiz5hxiY5wr5L76fyd8Kv" --note - 看看墨问「老池」是个怎样的创作者
mocli user info --uid "Qiz5hxiY5wr5L76fyd8Kv" --note
输出示例
{
"code": 0,
"status": "OK",
"reply": {
"info": {
"uid": "Qiz5hxiY5wr5L76fyd8Kv",
"name": "精卫鸟.",
"intro": "一只小小鸟,订阅我的没几个人,所以你们都是特殊的。。",
"regist_at": 1700000000
},
"counter": {
"user_follow": 12,
"user_follower": 345,
"note_pub": 28,
"note_fee": 3,
"note_album": 2
},
"note_idx": {
"note_top": ["note-top-1"],
"note_pub": ["note-pub-1", "note-pub-2"],
"note_fee": ["note-fee-1"],
"note_album": ["note-album-1"],
"note_popular": ["note-popular-1"]
},
"notes": {
"note-top-1": {
"note_id": "note-top-1",
"uid": "Qiz5hxiY5wr5L76fyd8Kv",
"title": "置顶笔记",
"brief": "这是一条置顶笔记摘要",
"url": "https://note.mowen.cn/detail/note-top-1?from=mocli"
}
}
}
}
reply 字段说明
| 字段 | 类型 | 说明 | 引用字段 |
|---|---|---|---|
info |
UserInfo | 目标用户基础信息。 | UserInfo - 用户信息 |
counter |
object | 用户计数信息,包含关注数、粉丝数、公开笔记数、付费笔记数和合集数。 | - |
note_idx |
object | 用户主页少量笔记样本的分类索引。仅使用 --note 时返回;每个分类通常只返回前若干条,不代表完整列表。 |
- |
notes |
map[string]NoteInfo | 笔记样本信息 Map,键为笔记 ID,值为笔记信息。仅使用 --note 时返回,用于辅助判断创作方向。 |
NoteInfo - 笔记信息 |
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 · 199 lines · 29 tokens per session scan A aedba011db68
mo-user is a skill published in the GitHub repository mowenxd/cli (33 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 3,222 once invoked, about $0.0001 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…