agentmods.dev

BoardGame: Command for Claude Code

.claude/commands/openspec/proposal.md

OpenSpec: Proposal is a command for Claude Code from zhuanggenhua/BoardGame. It costs 0 tokens per session (561 once invoked), scanned A, a copy of OpenSpec: Proposal, MIT.

A command for proposing a new OpenSpec change, where OpenSpec is a system for documenting planned software changes and their requirements.

In plain words
What is it for?
Use it to review the project, ask necessary questions, and create proposal, task, design, and specification-change documents.
Why use it?
It separates design approval from implementation and catches unclear requirements before code is written.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is zhuanggenhua/BoardGame's own configuration. It tells Claude Code how to work on BoardGame 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 BoardGame configures →

not rated 22repo today A scan 0 tokens copy · 95% MIT
View source ↗ zhuanggenhua/BoardGame
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/zhuanggenhua/BoardGame/main/.claude/commands/openspec/proposal.md
Clone the repo
git clone --depth 1 https://github.com/zhuanggenhua/BoardGame

Made for: Claude Code.

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/zhuanggenhua/boardgame/proposal.svg)](https://agentmods.dev/commands/zhuanggenhua/boardgame/proposal)
Your own site
<a href="https://agentmods.dev/commands/zhuanggenhua/boardgame/proposal"><img src="https://agentmods.dev/badge/commands/zhuanggenhua/boardgame/proposal.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 561 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 95% 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.00000 $0.00561
Opus 5 $0.00000 $0.00280
Sonnet 5 $0.00000 $0.00112
Haiku 4.5 $0.00000 $0.00056

Measured 8d ago against content hash cd62faf93b65, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 8d 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

95% identical to OpenSpec: Proposal — 2 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.

.claude/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 --no-interactive 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. 8d ago First seen · 29 lines · 0 tokens per session scan A cd62faf93b65

Subscribe to this mod's changes

OpenSpec: Proposal is a command published in the GitHub repository zhuanggenhua/BoardGame (22 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 tokens. A static security scan graded it A with 0 findings. It is 95% identical to OpenSpec: Proposal, differing in 2 lines, and is treated as a copy.

OpenSpecPlanning[openspec, change]
Related

Other commands, from other repositories

OpenSpec: Proposal

Scaffold a new OpenSpec change and validate strictly.

puppyone-ai/puppyone · 16 tokens

OpenSpec: Proposal

Scaffold a new OpenSpec change and validate strictly.

voicetreelab/voicetree · 0 tokens

OpenSpec: Proposal

Scaffold a new OpenSpec change and validate strictly.

sanyaden/agents0826 · 0 tokens

OpenSpec: Apply

Implement an approved OpenSpec change and keep tasks in sync.

puppyone-ai/puppyone · 17 tokens

OPSX: Continue

Continue working on a change - create the next artifact (Experimental).

intent-driven-dev/openspec-schemas · 18 tokens

update-docs

Research the current dhpk implementation and update user or agent docs without changing source semantics.

hmj1026/dhpk · 17 tokens