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-remarknpx skills add mowenxd/cli --skill mo-remarkgit 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.00127 | $0.01172 |
| Opus 5 | $0.00063 | $0.00586 |
| Sonnet 5 | $0.00025 | $0.00234 |
| Haiku 4.5 | $0.00013 | $0.00117 |
Grade A, and why
mo-remark 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
前置约束
CRITICAL — 先阅读 共享规则,其中包含 mocli 初始化、认证、输出解析以及安全规则
mocli remark - 墨问备注(remark -> uid)
本技能用于为墨问 UID 设置备注名(remark -> uid)、移除备注名 以及 使用备注名来检索墨问 UID,一个墨问 UID 可以设置多个备注名。
使用原则
- 当用户用人名、昵称、备注名指代某个墨问用户,且后续命令需要 UID 时,优先执行
mocli remark list --keyword <name>查找 UID。 - 如果备注命中唯一 UID,可直接把该 UID 用于后续命令。
- 如果备注命中多个 UID,展示备注名与 UID,让用户确认目标。
- 如果备注未命中,再使用
mo-user搜索用户,或询问用户提供 UID。 set和remove会修改本地备注配置,执行前必须确认用户意图。
mocli remark set
为一个墨问 UID 设置备注名,一个 UID 可以设置多个备注名。该命令会写入本地备注配置,执行前必须确认用户确实要新增备注。
使用示例
- 把 备注成老池
mocli remark set xxxxxx 老池 - 把 备注成池老师
mocli remark set xxxxxx 池老师
mocli remark remove
移除一个或多个备注条目。墨问 UID 或 备注名 只要有一项 完全匹配 keyword,对应条目就会被移除。该命令会修改本地备注配置,执行前必须确认用户确实要删除。
使用示例
- 删除老池的备注
mocli remark remove 老池 - 删除 的备注
mocli remark remove KBqt7yiVrXBa9DJIJuUm3
mocli remark list [--keyword string]
列出所有备注条目。可选参数 --keyword 用于筛选出备注名或 UID 中包含 keyword 的条目。
使用示例
- 查看我的备注列表
mocli remark list - 查看老池相关的备注
mocli remark list --keyword 老池
输出示例
without keyword
{
"code": 0,
"status": "OK",
"reply": {
"remarks": {
"me": "KBqt7yiVrXBa9DJIJuUm3",
"myself": "KBqt7yiVrXBa9DJIJuUm3",
"我": "KBqt7yiVrXBa9DJIJuUm3",
"池建强": "vtv_PV1fEMBb-8_BPlmDu",
"池老师": "vtv_PV1fEMBb-8_BPlmDu",
"精卫鸟zzz🇨🇳": "KBqt7yiVrXBa9DJIJuUm3",
"老池": "vtv_PV1fEMBb-8_BPlmDu"
}
}
}
with --keyword 池
{
"code": 0,
"status": "OK",
"reply": {
"remarks": {
"池建强": "vtv_PV1fEMBb-8_BPlmDu",
"池老师": "vtv_PV1fEMBb-8_BPlmDu",
"老池": "vtv_PV1fEMBb-8_BPlmDu"
}
}
}
reply 字段说明
| 字段 | 类型 | 说明 |
|---|---|---|
remarks |
map[string]string | key 备注名,value 墨问 UID |
结果解析规则
remarks的 key 是备注名,value 是墨问 UID。- 同一个 UID 可能对应多个备注名;展示时可按 UID 合并,减少重复。
- 作为后续命令参数时,只使用 UID,不要把备注名传给需要 UID 的参数。
- 如果
remarks为空,说明没有匹配备注,不要猜测 UID。
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 · 103 lines · 127 tokens per session scan A a6c27f3d3ae1
mo-remark is a skill published in the GitHub repository mowenxd/cli (33 stars, last pushed 8d ago), licensed MIT. It adds 127 tokens to every session and 1,172 once invoked, about $0.0006 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…