What is OpenSpec: Proposal?

A command for starting a new OpenSpec change proposal. OpenSpec is a project format for describing planned software changes before implementation.

Use it to review the project and existing specifications, create proposal and task files, identify open questions, and document design decisions for a new change.

It gives a change a defined structure and checks the proposal against the project's instructions before work begins.

OpenSpec: Proposal — Command by ivo-toby

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/ivo-toby/mcp-openapi-server/proposal

Clone the repo

git clone --depth 1 https://github.com/ivo-toby/mcp-openapi-server

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 518 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.

Model	Per session	Once invoked
Fable 5	$0.00016	$0.00518
Opus 5	$0.00008	$0.00259
Sonnet 5	$0.00003	$0.00104
Haiku 4.5	$0.00002	$0.00052

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

Security

Grade A, and why

OpenSpec: Proposal 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 OpenSpec: Proposal — 1 line 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.

.claude/commands/openspec/proposal.md · 28 lines

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 the openspec/ directory—run ls openspec or openspec update if you don't see it) if you need additional OpenSpec conventions or clarifications.
Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.

Steps

Review openspec/project.md, run openspec list and openspec list --specs, and inspect related code or docs (e.g., via rg/ls) to ground the proposal in current behaviour; note any gaps that require clarification.
Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under openspec/changes/<id>/.
Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
Draft spec deltas in changes/<id>/specs/<capability>/spec.md (one folder per capability) using ## ADDED|MODIFIED|REMOVED Requirements with at least one #### Scenario: per requirement and cross-reference related capabilities when relevant.
Draft tasks.md as an ordered list of small, verifiable work items that deliver user-visible progress, include validation (tests, tooling), and highlight dependencies or parallelizable work.
Validate with openspec validate <id> --strict and resolve every issue before sharing the proposal.

Reference

Use openspec show <id> --json --deltas-only or openspec show <spec> --type spec to inspect details when validation fails.
Search existing requirements with rg -n "Requirement:|Scenario:" openspec/specs before writing new ones.
Explore the codebase with rg <keyword>, ls, or direct file reads so proposals align with current implementation realities.

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.

3d ago First seen · 28 lines · 0 tokens per session scan A 3485e1f31a1a

Subscribe to this mod's changes

OpenSpec: Proposal is a command published in the GitHub repository ivo-toby/mcp-openapi-server (289 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to OpenSpec: Proposal, differing in 1 line, and is treated as a copy.

OpenSpec Planning [openspec, change]