Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ZTE-AICloud/Co-OmniSpec/plugin install omni-dsddWrote 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/zte-aicloud/co-omnispec/analyze)<a href="https://agentmods.dev/skills/zte-aicloud/co-omnispec/analyze"><img src="https://agentmods.dev/badge/skills/zte-aicloud/co-omnispec/analyze/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/zte-aicloud/co-omnispec/analyze"><img src="https://agentmods.dev/badge/skills/zte-aicloud/co-omnispec/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00066 | $0.03813 |
| Opus 5 | $0.00033 | $0.01906 |
| Sonnet 5 | $0.00013 | $0.00763 |
| Haiku 4.5 | $0.00007 | $0.00381 |
Grade A, and why
analyze 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 10d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OmniSpec 跨制品一致性与质量分析
目标
在三份制品齐备后, 识别 ${FEATURE_DIR} 下核心制品（spec.md、design.md、tasks.md）之间的不一致、重复、模糊和规范不足，并自动修复可消除项。前置条件：三份制品均已落盘。
用户输入
在继续之前，必须考虑用户的消息内容（若不为空）。
环境初始化
| 变量 | 含义 |
|---|---|
CLAUDE_PLUGIN_ROOT |
Omni 插件安装根目录 |
CLAUDE_WORKING_DIR |
用户工作区目录 |
FEATURE_DIR |
特性目录（绝对路径，应在 ${CLAUDE_WORKING_DIR}/changes/... 下） |
路径约定
| 制品 | 路径 |
|---|---|
| 规范 | ${FEATURE_DIR}/spec.md |
| 设计 | ${IMPL_DESIGN} 或 ${FEATURE_DIR}/design.md |
| 任务 | ${TASKS} 或 ${FEATURE_DIR}/tasks.md |
| 章程 | ${CLAUDE_WORKING_DIR}/.omni-infra/memory/constitution.md |
| 环境文件 | ${FEATURE_DIR}/.runs/env.sh |
Step 0.1 检查变量
test -n "${CLAUDE_PLUGIN_ROOT:-}" && test -d "${CLAUDE_PLUGIN_ROOT}"
test -n "${CLAUDE_WORKING_DIR:-}" && test -d "${CLAUDE_WORKING_DIR}"
两项均通过且已 source 过 env.sh、FEATURE_DIR 非空 → 进入步骤 1。否则执行 Step 0.2。
Step 0.2 补全变量（仅执行一次）
CLAUDE_PLUGIN_ROOT
- 若 Claude Code 已注入且目录存在：沿用。
- 若仍缺失，按顺序降级（须验证
${路径}/skills/analyze/SKILL.md存在）：- Skill 加载上下文中的插件安装根；
- 在
${CLAUDE_WORKING_DIR}或其上级查找含.claude-plugin/plugin.json的目录；
export CLAUDE_PLUGIN_ROOT="<绝对路径>"- 失败 → 终止并提示配置插件。
CLAUDE_WORKING_DIR
- 若已注入且目录存在：沿用。
- 若缺失：
export CLAUDE_WORKING_DIR="$(pwd)"（不用git rev-parse --show-toplevel） - 失败 → 终止。
Step 0.3 校验（必须通过）
test -f "${CLAUDE_PLUGIN_ROOT}/scripts/bash/check-prerequisites.sh"
test -f "${CLAUDE_PLUGIN_ROOT}/skills/design/scripts/bash/design-resolve-context.sh"
test -d "${CLAUDE_WORKING_DIR}"
路径拼接约定
- 插件脚本：
${CLAUDE_PLUGIN_ROOT}/scripts/bash/... - 前置检查在
CLAUDE_WORKING_DIR下执行 - 禁止用 Git 分支推断
FEATURE_DIR；须以env.sh/paths.json/design-resolve-context.sh为准
操作约束
- 允许编辑
${FEATURE_DIR}下spec.md、design.md、tasks.md（及修复所必需的最小范围）。 - 完成步骤 1–6 后 必须进入步骤 7 修复—验证循环；不设轮数上限，直至单轮无可自动修复项（收敛）。
- 禁止向用户确认「是否修复/继续」；禁止只读报告代替自动修复。
- 残留问题不得阻断：收敛后须完整打印残留项；本技能仍正常完成，禁止将残留问题记为技能失败。
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.
- 10d ago First seen · 307 lines · 66 tokens per session scan A 8783a5259cff
analyze is a skill published in the GitHub repository ZTE-AICloud/Co-OmniSpec (54 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 3,813 once invoked, about $0.0003 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.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…