specsync-create-change

specsync-create-change is a command for Cursor from CorvidLabs/agent-3md. It costs 0 tokens per session (119 once invoked), scanned A, a copy of create-change, MIT.

A command that starts a verified spec-sync change from a supplied description. It asks questions one at a time and records the answers.

In plain words
What is it for?
Use it to interview the user about a proposed change, select the needed documents, and show the next permitted action.
Why use it?
It makes the change-planning process repeatable and keeps implementation and approval as separate stages.

Command for Cursor

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/corvidlabs/agent-3md/specsync-create-change
Clone the repo
git clone --depth 1 https://github.com/CorvidLabs/agent-3md

Made for: Cursor.

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 specsync-create-change

README.md
[![agentmods](https://agentmods.dev/badge/commands/corvidlabs/agent-3md/specsync-create-change.svg)](https://agentmods.dev/commands/corvidlabs/agent-3md/specsync-create-change)
Your own site
<a href="https://agentmods.dev/commands/corvidlabs/agent-3md/specsync-create-change"><img src="https://agentmods.dev/badge/commands/corvidlabs/agent-3md/specsync-create-change.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 119 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% 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 $0.00000 $0.00119
Opus 5 $0.00000 $0.00060
Sonnet 5 $0.00000 $0.00024
Haiku 4.5 $0.00000 $0.00012

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

Security

Grade A, and why

specsync-create-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 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.

Origin

This is a copy

91% identical to create-change — 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.

.cursor/commands/specsync-create-change.md · 10 lines

What it actually says

Create a verified spec-sync SDD change.

Arguments: $ARGUMENTS

  1. Run specsync change new "$ARGUMENTS" --json.
  2. Read the returned questions array and interview the user one question at a time.
  3. Record each answer with specsync change answer <id> <question-id> <answer> --json.
  4. Continue until the question list is empty, then show the selected artifacts and next action.
  5. Do not approve, implement, verify, accept, or archive until the corresponding human gate or work stage is reached.
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 · 10 lines · 0 tokens per session scan A 62ddba7a5215

Subscribe to this mod's changes

specsync-create-change is a command published in the GitHub repository CorvidLabs/agent-3md (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 119 tokens. A static security scan graded it A with 0 findings. It is 91% identical to create-change, differing in 7 lines, and is treated as a copy.