Borrowing it
Nothing to install: this file belongs to datenoio/iterabledata. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/datenoio/iterabledata/main/.cursor/commands/openspec-proposal.mdgit clone --depth 1 https://github.com/datenoio/iterabledataWrote 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.
[](https://agentmods.dev/commands/datenoio/iterabledata/openspec-proposal)<a href="https://agentmods.dev/commands/datenoio/iterabledata/openspec-proposal"><img src="https://agentmods.dev/badge/commands/datenoio/iterabledata/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.
<a href="https://agentmods.dev/commands/datenoio/iterabledata/openspec-proposal"><img src="https://agentmods.dev/badge/commands/datenoio/iterabledata/openspec-proposal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.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 |
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 1mo 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.
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.
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 theopenspec/directory—runls openspecoropenspec updateif 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
- Review
openspec/project.md, runopenspec listandopenspec list --specs, and inspect related code or docs (e.g., viarg/ls) to ground the proposal in current behaviour; note any gaps that require clarification. - Choose a unique verb-led
change-idand scaffoldproposal.md,tasks.md, anddesign.md(when needed) underopenspec/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.mdwhen 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 Requirementswith at least one#### Scenario:per requirement and cross-reference related capabilities when relevant. - Draft
tasks.mdas 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> --strictand resolve every issue before sharing the proposal.
Reference
- Use
openspec show <id> --json --deltas-onlyoropenspec show <spec> --type specto inspect details when validation fails. - Search existing requirements with
rg -n "Requirement:|Scenario:" openspec/specsbefore writing new ones. - Explore the codebase with
rg <keyword>,ls, or direct file reads so proposals align with current implementation realities.
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.
- 1mo ago First seen · 29 lines · 17 tokens per session scan A 6156bc7108e6
/openspec-proposal is a command published in the GitHub repository datenoio/iterabledata (37 stars, last pushed 2mo 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.
Other commands, from other repositories
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OpenSpec: Archive
Archive a deployed OpenSpec change and update specs.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
INDEX
Navigation index for dhpk plugin commands. Internal documentation; not an invocable command.
create-release
Cuts a new release of a software project or plugin, coordinating release configuration, version files, changelog, validation, and the fixed git/PR/tag/CI sequence. Not for: PHP package publication or ordinary commits. Output: a validated release preparation or publication result with the human merge gate preserved.
doc-refactor
Maintain documentation through stale-doc refresh, architecture codemap generation, or a bounded Markdown refactor. Selects update, codemap, or refactor while preserving each output and evidence contract. Not for application source, tests, manifests, route tables, generated projections, or broad policy review.