agentmods.dev

close-spec

A command that archives a completed OpenSpec change, where an OpenSpec change is a named set of proposed project work. It checks that the command-line tool and change exist before archiving.

In plain words
What is it for?
Run `/close-spec <change-name>` from the documentation directory after an OpenSpec change is complete.
Why use it?
It removes completed changes from the active list and reports missing prerequisites or failed archive operations.

Command for Cursor

435 +1 2d ago A scan 9 tokens original Apache-2.0
View the source file jabrena/plinth
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 commands/jabrena/plinth/close-spec
Clone the repo
git clone --depth 1 https://github.com/jabrena/plinth

Made for: Cursor.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 399 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00009 $0.00399
Opus 5 $0.00005 $0.00199
Sonnet 5 $0.00002 $0.00080
Haiku 4.5 $0.00001 $0.00040

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

Security

Grade A, and why

close-spec 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.

.cursor/commands/close-spec.md · 49 lines

What it actually says

close-spec

Archive an OpenSpec change by name, using the OpenSpec CLI, so completed changes can be reconciled and removed from the active change list.

Usage

/close-spec <change-name>

Inputs

  • <change-name>: the OpenSpec change name to archive (for example add-close-spec-command)

Owner

@plinth-architect

Workflow

  1. Validate the argument is present.
    • If missing, print usage: /close-spec <change-name> and stop.
  2. Verify the OpenSpec CLI is available (for example, openspec --version).
    • If OpenSpec cannot be executed, report the missing prerequisite and provide a short hint to install/enable OpenSpec.
  3. Verify the change exists before attempting to archive it.
    • Prefer checking openspec list and matching <change-name>, or
    • Use openspec show <change-name> and treat “not found” as an unknown-change error.
    • If the change is unknown, report that the change was not found and suggest running openspec list.
  4. From the documentation/ working directory, execute the equivalent of:
    • openspec archive <change-name>
  5. If the archive command fails, surface the OpenSpec CLI output and stop (do not claim success).
  6. If the archive command succeeds, report a success message that includes <change-name>.

Safeguards

  • Do not guess or auto-correct the change name.
  • Do not claim success when openspec archive fails; surface the CLI output.
  • Do not run openspec archive unless the change exists.
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. 3d ago First seen · 49 lines · 9 tokens per session scan A 5d18c50d32c8

Subscribe to this mod's changes

close-spec is a command published in the GitHub repository jabrena/plinth (435 stars, last pushed 2d ago), licensed Apache-2.0. It adds 9 tokens to every session and 399 once invoked, about $0.0000 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.

Project managementagent-skillsai-skillsclaudeclaude-agentsclaude-codeclaude-code-skills
Related

Other commands, from other repositories

ai-do

You are a routing assistant for DSPy AI skills. Understand the user's problem, pick the best skill, and generate a ready-to-run prompt.

lebsral/DSPy-Programming-not-prompting-LMs-skills · 0 tokens

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens