tdd-mcp-server: Skill for Claude Code

.agents/skills/openspec-archive-change/SKILL.md

openspec-archive-change is a skill for Claude Code from laonayan/tdd-mcp-server. It costs 50 tokens per session (3,676 once invoked), scanned A, a copy of openspec-archive-change, MIT.

A workflow for archiving a completed OpenSpec change after its implementation is finished. Archiving moves the change into the project's record of completed work.

In plain words
What is it for?
Checking that an OpenSpec project exists, confirming a change is complete, and moving it into the archive with the correct repository store.
Why use it?
It keeps finished planning documents organised and helps ensure the project is ready before finalising a change.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents); mentions Codex; $skill-name invocation.

This is laonayan/tdd-mcp-server's own configuration. It tells Claude Code how to work on tdd-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tdd-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to laonayan/tdd-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/laonayan/tdd-mcp-server/master/.agents/skills/openspec-archive-change/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/laonayan/tdd-mcp-server

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/laonayan/tdd-mcp-server/openspec-archive-change/github.svg)](https://agentmods.dev/skills/laonayan/tdd-mcp-server/openspec-archive-change)
Your own site
<a href="https://agentmods.dev/skills/laonayan/tdd-mcp-server/openspec-archive-change"><img src="https://agentmods.dev/badge/skills/laonayan/tdd-mcp-server/openspec-archive-change/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 openspec-archive-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/laonayan/tdd-mcp-server/openspec-archive-change"><img src="https://agentmods.dev/badge/skills/laonayan/tdd-mcp-server/openspec-archive-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,676 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 98% copy Near-identical to another mod 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.00050 $0.03676
Opus 5.5 $0.00020 $0.01470
Sonnet 5.5 $0.00010 $0.00735
Haiku 4.5 $0.00005 $0.00368

Measured 4d ago against content hash d36c13d4ecc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 4d 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.

Origin

This is a copy

98% identical to openspec-archive-change — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/openspec-archive-change/SKILL.md · 222 lines

How it starts

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

Archive a completed change in the experimental workflow.

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Project check: These steps expect a project that already uses OpenSpec. Before the first step that writes anything (new change, archive, sync specs, or authoring an artifact file), confirm the project has a root: run openspec list --json (with --store <id> when a store is selected, since the store is then the root) and read root. A root object means the project is set up. "root": null means it is not - there is no openspec/ directory here, and a write such as openspec new change would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.

One "root": null is not about setup: when a status error message starts with Declared in or Invalid store declaration in and names this project's openspec/config.yaml (or config.yml), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the store: line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's message and fix.

Otherwise, with no root, what happens next depends on how this workflow was reached:

  • Auto-selected: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
  • Explicit OpenSpec request: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (openspec init), target a store they already have (--store <id>), or continue without OpenSpec for this request. Wait for their answer.

In both branches, never create the root as a side effect: do not run openspec init until the user asks for it, do not hand-create openspec/ files, and do not let a command create it.

<capability-path> is the spec directory relative to specs/ (for example, user-auth or identity/user-auth). Preserve the full path from each delta spec when resolving its main spec.

Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

  1. Select the change

    If a name is provided, use it. Otherwise:

    • Infer from conversation context if the user mentioned a change
    • Auto-select if only one active change exists
    • If ambiguous, run openspec list --json to get available changes and ask the user to select one

    When prompting, show only active changes (not already archived). Include the schema used for each change if available.

    Always announce: "Using change: " and how to override (e.g., $openspec-archive-change (Codex) or /openspec-archive-change (other agents) <other>).

    Load current archive inputs before the existing archive checks:

Read the full file on GitHub · 222 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. 4d ago First seen · 222 lines · 50 tokens per session scan A d36c13d4ecc7

Subscribe to this mod's changes

openspec-archive-change is a skill published in the GitHub repository laonayan/tdd-mcp-server (2 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 3,676 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to openspec-archive-change, differing in 4 lines, and is treated as a copy.

Related

openspec-archive-change compared with skills from other repositories

openspec-archive-change next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
openspec-archive-changelaonayan/tdd-mcp-serverSkill2yesterdayMITA50Claude Code
imagegenopenai/codexSkill135ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill395ktodayMITA36Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill80k9d agoMITA200Claude Code, Codex
next-cache-components-adoptionvercel/next.jsSkill144ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex