Borrowing it
Nothing to install: this file belongs to zhuanggenhua/BoardGame. 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/zhuanggenhua/BoardGame/main/.opencode/command/openspec-archive.mdgit clone --depth 1 https://github.com/zhuanggenhua/BoardGameWrote 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/zhuanggenhua/boardgame/openspec-archive)<a href="https://agentmods.dev/commands/zhuanggenhua/boardgame/openspec-archive"><img src="https://agentmods.dev/badge/commands/zhuanggenhua/boardgame/openspec-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.
<a href="https://agentmods.dev/commands/zhuanggenhua/boardgame/openspec-archive"><img src="https://agentmods.dev/badge/commands/zhuanggenhua/boardgame/openspec-archive.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.00010 | $0.00441 |
| Opus 5 | $0.00005 | $0.00220 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $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 3d 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
97% identical to openspec-archive — 7 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
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 --strict --no-interactiveand 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.
- 3d ago First seen · 28 lines · 10 tokens per session scan A f6e427086e24
openspec-archive is a command published in the GitHub repository zhuanggenhua/BoardGame (23 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to openspec-archive, differing in 7 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.