Borrowing it
Nothing to install: this file belongs to atman-33/kiro-for-codex-ide. 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/atman-33/kiro-for-codex-ide/main/.codex/prompts/openspec-create-change-proposal.mdgit clone --depth 1 https://github.com/atman-33/kiro-for-codex-ideWrote 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/atman-33/kiro-for-codex-ide/openspec-create-change-proposal)<a href="https://agentmods.dev/commands/atman-33/kiro-for-codex-ide/openspec-create-change-proposal"><img src="https://agentmods.dev/badge/commands/atman-33/kiro-for-codex-ide/openspec-create-change-proposal.svg" alt="Measured on agentmods" 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.00000 | $0.00155 |
| Opus 5 | $0.00000 | $0.00077 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
openspec-create-change-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.
What it actually says
openspec-create-change-proposal
You are an assistant that helps users create OpenSpec change proposals for new features.
Instructions
-
Confirm the Feature
-
Before starting, ask the user to describe the feature they want to add in detail.
-
Clarify its purpose, scope, and any relevant context (e.g., related specs, modules, or dependencies).
-
Example questions:
- “What feature would you like to add?”
- “Could you explain how this feature fits into the current system?”
- “Are there any related components or constraints I should be aware of?”
-
-
Create the OpenSpec Change Proposal
- Once the feature is confirmed, create an OpenSpec change proposal for this feature.
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.
- 8d ago First seen · 20 lines · 0 tokens per session scan A 7cdc4d8e372b
openspec-create-change-proposal is a command published in the GitHub repository atman-33/kiro-for-codex-ide (16 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 155 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
speckit.companion.plan
Companion plan — implementation plan with research & design artifacts.
speckit.companion.specify
Companion specify — spec.md with prioritized user stories.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
speckit.companion.tasks
Companion tasks — user-story phased task list.
speckit.companion.auto
Companion auto — run the whole pipeline hands-off (specify → plan → tasks → implement → mark-complete), no pauses.
speckit.companion.living-adopt
Brownfield adoption wizard — draft living specs for the code areas you name, central or colocated, and register them (opt-in, surface-first, [DRAFT]).