Borrowing it
Nothing to install: this file belongs to TuanLdv/mcp-openapi-server-demo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TuanLdv/mcp-openapi-server-demo/master/.cursor/commands/openspec-archive.mdgit clone --depth 1 https://github.com/TuanLdv/mcp-openapi-server-demoWrote 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/commands/tuanldv/mcp-openapi-server-demo/openspec-archive)<a href="https://agentmods.dev/commands/tuanldv/mcp-openapi-server-demo/openspec-archive"><img src="https://agentmods.dev/badge/commands/tuanldv/mcp-openapi-server-demo/openspec-archive.svg" alt="Measured on agentmods" 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.00016 | $0.00443 |
| Opus 5 | $0.00008 | $0.00221 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
/openspec-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 5d 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.
This is a copy
92% identical to OpenSpec: Archive — 6 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.
What it actually says
Guardrails
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome.
- Refer to
openspec/AGENTS.md(located inside theopenspec/directory—runls openspecoropenspec updateif you don't see it) if you need additional OpenSpec conventions or clarifications.
Steps
- Determine the change ID to archive:
- If this prompt already includes a specific change ID (for example inside a
<ChangeId>block populated by slash-command arguments), use that value after trimming whitespace. - If the conversation references a change loosely (for example by title or summary), run
openspec listto surface likely IDs, share the relevant candidates, and confirm which one the user intends. - Otherwise, review the conversation, run
openspec list, and ask the user which change to archive; wait for a confirmed change ID before proceeding. - If you still cannot identify a single change ID, stop and tell the user you cannot archive anything yet.
- If this prompt already includes a specific change ID (for example inside a
- Validate the change ID by running
openspec list(oropenspec show <id>) and stop if the change is missing, already archived, or otherwise not ready to archive. - Run
openspec archive <id> --yesso the CLI moves the change and applies spec updates without prompts (use--skip-specsonly for tooling-only work). - Review the command output to confirm the target specs were updated and the change landed in
changes/archive/. - Validate with
openspec validate --strictand inspect withopenspec show <id>if anything looks off.
Reference
- Use
openspec listto confirm change IDs before archiving. - Inspect refreshed specs with
openspec list --specsand address any validation issues before handing off.
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.
- 5d ago First seen · 28 lines · 16 tokens per session scan A 66267e21f7b1
/openspec-archive is a command published in the GitHub repository TuanLdv/mcp-openapi-server-demo (0 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to OpenSpec: Archive, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
update-docs
Research the current dhpk implementation and update user or agent docs without changing source semantics.
verify
Verify a repository in fast or full mode with runner-first execution, deterministic stage order, and explicit PASS/FAIL/SKIP output.
dep-audit
Audit dependency security risks.
harness-govern
Explicit harness governance front door with health, budget, fill, revise, and sync modes; each mode preserves its own evidence and mutation boundary.