openspec-archive-change

A tool for moving a completed OpenSpec change into an archive after its implementation is finished. An archive is a stored record of work that is no longer active.

In plain words
What is it for?
Use it to finalize and archive a completed change in the experimental OpenSpec workflow.
Why use it?
It provides a final step for closing completed changes and keeping their records organized.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/taberoajorge/loopforge/openspec-archive-change
Any agent
npx skills add taberoajorge/loopforge --skill openspec-archive-change
Clone the repo
git clone --depth 1 https://github.com/taberoajorge/loopforge

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 952 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00031 $0.00952
Opus 5 $0.00015 $0.00476
Sonnet 5 $0.00006 $0.00190
Haiku 4.5 $0.00003 $0.00095

Measured 2d ago against content hash dd8783f590c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/skills/openspec-archive-change/SKILL.md · 115 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 115 lines · 31 tokens per session scan A dd8783f590c0

Subscribe to this mod's changes

openspec-archive-change is a skill published in the GitHub repository taberoajorge/loopforge (3 stars, last pushed 1mo ago), with no licence file. It adds 31 tokens to every session and 952 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories