agentmods.dev

antd-components-mcp: Command for Claude Code

.cursor/commands/openspec-proposal.md

/openspec-proposal is a command for Claude Code, Cursor from zhixiaoqiang/antd-components-mcp. It costs 17 tokens per session (557 once invoked), scanned A, a copy of openspec-proposal, MIT.

A command that creates planning documents for a proposed OpenSpec change before any code is written. OpenSpec is a system for describing software changes, their design, and their tasks.

In plain words
What is it for?
Use it to inspect the project, identify missing details, create proposal files, and define requirements and tasks for a future change.
Why use it?
It turns an unclear request into a reviewed plan and separates approval from implementation.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md). Also seen: mentions AGENTS.md.

This is zhixiaoqiang/antd-components-mcp's own configuration. It tells Claude Code and Cursor how to work on antd-components-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything antd-components-mcp configures →

not rated 246repo 11d ago A scan 17 tokens copy · 89% MIT
View source ↗ zhixiaoqiang/antd-components-mcp npmjs.com
Reuse

Borrowing it

Nothing to install: this file belongs to zhixiaoqiang/antd-components-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zhixiaoqiang/antd-components-mcp/main/.cursor/commands/openspec-proposal.md
Clone the repo
git clone --depth 1 https://github.com/zhixiaoqiang/antd-components-mcp

Made for: Claude Code, 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 /openspec-proposal

README.md
[![agentmods](https://agentmods.dev/badge/commands/zhixiaoqiang/antd-components-mcp/openspec-proposal/github.svg)](https://agentmods.dev/commands/zhixiaoqiang/antd-components-mcp/openspec-proposal)
Your own site
<a href="https://agentmods.dev/commands/zhixiaoqiang/antd-components-mcp/openspec-proposal"><img src="https://agentmods.dev/badge/commands/zhixiaoqiang/antd-components-mcp/openspec-proposal/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.

agentmods 80×15 button for /openspec-proposal

Your own site · 80×15
<a href="https://agentmods.dev/commands/zhixiaoqiang/antd-components-mcp/openspec-proposal"><img src="https://agentmods.dev/badge/commands/zhixiaoqiang/antd-components-mcp/openspec-proposal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 557 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% 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.1 $0.00017 $0.00557
Opus 5.5 $0.00007 $0.00223
Sonnet 5.5 $0.00003 $0.00111
Haiku 4.5 $0.00002 $0.00056

Measured 2mo ago against content hash 6156bc7108e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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

89% identical to openspec-proposal — 5 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/openspec-proposal.md · 29 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.
  • Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.

Steps

  1. 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.
  2. Choose a unique verb-led change-id and scaffold proposal.md, tasks.md, and design.md (when needed) under openspec/changes/<id>/.
  3. Map the change into concrete capabilities or requirements, breaking multi-scope efforts into distinct spec deltas with clear relationships and sequencing.
  4. Capture architectural reasoning in design.md when the solution spans multiple systems, introduces new patterns, or demands trade-off discussion before committing to specs.
  5. 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.
  6. 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.
  7. 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.

  1. 2mo ago First seen · 29 lines · 17 tokens per session scan A 6156bc7108e6

Subscribe to this mod's changes

/openspec-proposal is a command published in the GitHub repository zhixiaoqiang/antd-components-mcp (246 stars, last pushed 11d ago), licensed MIT. It adds 17 tokens to every session and 557 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to openspec-proposal, differing in 5 lines, and is treated as a copy.

OpenSpecPlanningantdantd-designmcp
Related

/openspec-proposal compared with commands from other repositories

/openspec-proposal next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
/openspec-proposalzhixiaoqiang/antd-components-mcpCommand24611d agoMITA17Claude Code, Cursor
opsx-bulk-archiveintent-driven-dev/intent-driven-templateCommand19422d agoMITA6Claude Code, OpenCode
build-fixerTenon-Net/TenonAdminCommand4114d agoApache-2.0A15Claude Code, Codex
information-architectTenon-Net/TenonAdminCommand4114d agoApache-2.0A14Claude Code, Codex
code-simplifierTenon-Net/TenonAdminCommand4114d agoApache-2.0A34Codex
plannerTenon-Net/TenonAdminCommand4114d agoApache-2.0A12Claude Code, Codex
product-managerTenon-Net/TenonAdminCommand4114d agoApache-2.0A16Claude Code, Codex