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-taggit 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-tag)<a href="https://agentmods.dev/skills/mowenxd/cli/mo-tag"><img src="https://agentmods.dev/badge/skills/mowenxd/cli/mo-tag/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-tag"><img src="https://agentmods.dev/badge/skills/mowenxd/cli/mo-tag.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00063 | $0.01284 |
| Opus 5.5 | $0.00025 | $0.00514 |
| Sonnet 5.5 | $0.00013 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
mo-tag 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 2mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
前置约束
CRITICAL — 先阅读 共享规则,其中包含 mocli 初始化、认证、输出解析以及安全规则
mocli tag - 墨问标签
本技能用于读取 当前认证用户 的标签列表。当前只支持获取我的笔记标签,不会创建、删除、重命名或绑定标签。
命令选择规则
- 用户要“查看我的标签/获取我的标签/列出我的笔记标签/我有哪些标签”时,使用
mocli tag mine。 - 用户要“从已有标签里选出 X 个标签,再给某篇笔记打标签/改标签”时,先使用
mocli tag mine获取候选标签,再结合mo-note的mocli note tag完成写入。 - 用户没有说明标签类型时,默认按笔记标签处理,即使用
--filter note或省略--filter。 - 用户要“给某篇笔记加标签/删除某篇笔记标签/覆盖某篇笔记标签”时,不使用本技能,改用
mo-note的mocli note tag。 - 用户要“查看某个/某些标签下的笔记、按标签筛选笔记”时,不使用本技能,改用
mo-note的mocli notes tagged;需要先从已有标签中挑选时,先用mocli tag mine获取候选标签的名称和 ID。 - 用户要“创建一个空标签/重命名标签/删除标签本身”时,说明当前 CLI 暂不支持该能力,不要用
mocli tag mine假装执行写入。
mocli tag mine [--filter]
本命令用于获取当前认证用户的标签列表。它是读取操作,不会修改任何笔记或标签。
可选参数:
--filter string:标签类型。当前只支持note,表示我的笔记标签;不传时默认也是note。
使用原则
- 默认执行
mocli tag mine即可;只有需要显式表达过滤条件时才加--filter note。 - 如果用户传入或要求非
note的过滤条件,说明当前只支持note,不要尝试其它值。 - 执行后按共享规则解析顶层
code、status、reason;成功时展示reply.tags,失败时展示reason、msg、meta.hints等可执行信息。 - 如果
reply.tags为空,明确说明当前没有返回标签,不要编造标签名。
使用示例
- 查看我的标签
mocli tag mine - 查看我的笔记标签
mocli tag mine --filter note
从已有标签中选择后给笔记打标签
当用户希望“从已有标签中选 X 个标签给某篇笔记打标签”时,按以下流程处理:
- 先执行
mocli tag mine获取已有标签候选。 - 按用户要求筛选或展示候选标签;如果用户只说“选 X 个”,但没有给筛选规则,先展示候选并请用户确认具体标签,不要擅自挑选。
- 用户确认标签后,切换到
mo-note执行mocli note tag。用户说“打上/追加这些标签”时用--append;用户说“标签就设为这些/只保留这些”时用--reset。 - 写入前仍需按
mo-note规则确认目标笔记 ID、操作类型和最终标签列表。
示例流程:
mocli tag mine
mocli note tag --note-id note-123 --append "AI,产品思考"
输出示例
{
"code": 0,
"status": "OK",
"reply": {
"tags": [
{
"id": 11,
"name": "AI"
},
{
"id": 12,
"name": "产品思考"
}
]
}
}
reply 字段说明
| 字段 | 类型 | 说明 |
|---|---|---|
tags |
array | 当前认证用户的标签列表。当前只返回笔记标签。 |
tags[].id |
integer | 标签 ID,可用于精确识别同名或后续接口扩展。 |
tags[].name |
string | 标签名称,通常是展示给用户的主要字段。 |
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.
- 2mo ago First seen · 102 lines · 63 tokens per session scan A 58f67a4f2414
mo-tag is a skill published in the GitHub repository mowenxd/cli (40 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,284 once invoked, about $0.0003 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.