archive

archive is a skill for Claude Code from ZTE-AICloud/Co-OmniSpec. It costs 68 tokens per session (3,454 once invoked), scanned A, original, MIT.

A documentation update step that carries approved feature changes into a central set of requirements, scenarios, entities, functions, and interface documents.

In plain words
What is it for?
Use it after a feature change when its requirements, behavior, data model, functions, or interfaces must be reflected in the project documentation.
Why use it?
It keeps the project’s formal documentation aligned with the feature specifications and design files used during implementation.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the omni-dsdd plugin — 40 skills, 16 agents, 1 hook shipped together

Good fit Use it after a feature change when its requirements, behavior, data model, functions, or interfaces must be reflected in the project documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zte-aicloud/co-omnispec/archive
Install

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.

Any agent
npx skills add ZTE-AICloud/Co-OmniSpec --skill archive
Clone the repo
git clone --depth 1 https://github.com/ZTE-AICloud/Co-OmniSpec

Made for: Claude Code.

Or install omni-dsdd, the plugin that ships this one along with the rest of its 40 skills, 16 agents, 1 hook.

Wrote 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.

agentmods badge for archive

README.md
[![agentmods](https://agentmods.dev/badge/skills/zte-aicloud/co-omnispec/archive/github.svg)](https://agentmods.dev/skills/zte-aicloud/co-omnispec/archive)
Your own site
<a href="https://agentmods.dev/skills/zte-aicloud/co-omnispec/archive"><img src="https://agentmods.dev/badge/skills/zte-aicloud/co-omnispec/archive/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.

agentmods 80×15 button for archive

Your own site · 80×15
<a href="https://agentmods.dev/skills/zte-aicloud/co-omnispec/archive"><img src="https://agentmods.dev/badge/skills/zte-aicloud/co-omnispec/archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,454 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.03454
Opus 5 $0.00034 $0.01727
Sonnet 5 $0.00014 $0.00691
Haiku 4.5 $0.00007 $0.00345

Measured 10d ago against content hash 112524acefee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

archive 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.

omni-dsdd/skills/archive/SKILL.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

archive

将变更目录中的变更指示文件(spec.md/design.md/contracts/*.md)解析并应用到 DOC_DIR/specs/ 下的要素文档,保持规范文档与变更实现的一致性。

输入

  • 配置脚本输出(必需)
    • Windows: scripts/powershell/check-prerequisites.ps1 --json --paths-only
    • Linux: scripts/bash/check-prerequisites.sh --json --paths-only
    • 期望字段REPO_ROOTBRANCHFEATURE_DIRFEATURE_SPECIMPL_DESIGNCHANGES_DIR(即 FEATURE_DIR)、DOC_DIRDOC_SPECS_DIR
  • 变更文件(必需)(都位于 CHANGES_DIR 下):
    • spec.md:需求与场景变更(参考 spec-template.md
    • design.md:逻辑实体与功能变更(参考 design-template.md
    • contracts/*.md:接口文档变更(参考 interface-template.md
  • 模板文件(必需)(位于 .omni-infra/metamodel/):
    • 1.requirement-template.md
    • 3.scenario-template.md
    • 5.function-template.md
    • 6.entity-template.md
    • 7.interface-template.md
  • 现有规范文档与清单/关联文件(如存在)
    • DOC_DIR/specs/requirements/*.mdDOC_DIR/specs/requirements/requirements.json
    • DOC_DIR/specs/scenarios/*.mdDOC_DIR/specs/scenarios/0.scenario_list.md
    • DOC_DIR/specs/logic_entities/*.mdDOC_DIR/specs/logic_entities/0.entity_list.md
    • DOC_DIR/specs/functions/*.mdDOC_DIR/specs/functions/0.function_list.mdDOC_DIR/specs/functions/functions.json
    • DOC_DIR/specs/interfaces/*.mdDOC_DIR/specs/interfaces/0.interface_list.mdDOC_DIR/specs/interfaces/interface.json

输出

  • 更新后的要素文档
    • 需求:DOC_DIR/specs/requirements/REQ-XXX-*.md
    • 场景:DOC_DIR/specs/scenarios/SCN-XXX-*.md
    • 逻辑实体:DOC_DIR/specs/logic_entities/ENTITY-XXX-*.md
    • 功能:DOC_DIR/specs/functions/FUNC-XXX-*.md
    • 接口:DOC_DIR/specs/interfaces/API-XXX-*.md
  • 更新后的清单与关联关系文件
    • DOC_DIR/specs/scenarios/0.scenario_list.md
    • DOC_DIR/specs/logic_entities/0.entity_list.md
    • DOC_DIR/specs/functions/0.function_list.md(如存在)
    • DOC_DIR/specs/requirements/requirements.json
    • DOC_DIR/specs/functions/functions.json
    • DOC_DIR/specs/interfaces/interface.json
  • 执行结果摘要(由 Agent 输出的自然语言报告):
    • 新增/修改/删除的文档列表
    • 关联关系更新情况
    • 检测到的错误或需要人工确认的冲突

Read the full file on GitHub · 241 lines

Changes

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.

  1. 10d ago First seen · 241 lines · 68 tokens per session scan A 112524acefee

Subscribe to this mod's changes

archive is a skill published in the GitHub repository ZTE-AICloud/Co-OmniSpec (54 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 3,454 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens