event-store-adapter-js: Command for Claude Code

.claude/commands/kiro/spec-quick.md

spec-quick is a command for Claude Code from j5ik2o/event-store-adapter-js. It costs 8 tokens per session (2,581 once invoked), scanned A, a copy of spec-quick, Apache-2.0.

A command that creates a software specification through four stages: setup, requirements, design, and tasks. It can either ask for approval at each stage or run automatically.

In plain words
What is it for?
For generating requirements, technical design, and task lists for a proposed software change.
Why use it?
It turns an idea into an organized implementation plan in one workflow.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the SlashCommand tool; positional $N argument.

This is j5ik2o/event-store-adapter-js's own configuration. It tells Claude Code how to work on event-store-adapter-js 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 event-store-adapter-js configures →

Reuse

Borrowing it

Nothing to install: this file belongs to j5ik2o/event-store-adapter-js. 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/j5ik2o/event-store-adapter-js/main/.claude/commands/kiro/spec-quick.md
Clone the repo
git clone --depth 1 https://github.com/j5ik2o/event-store-adapter-js

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 spec-quick

README.md
[![agentmods](https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/spec-quick.svg)](https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/spec-quick)
Your own site
<a href="https://agentmods.dev/commands/j5ik2o/event-store-adapter-js/spec-quick"><img src="https://agentmods.dev/badge/commands/j5ik2o/event-store-adapter-js/spec-quick.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,581 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 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.02581
Opus 5 $0.00004 $0.01290
Sonnet 5 $0.00002 $0.00516
Haiku 4.5 $0.00001 $0.00258

Measured 5d ago against content hash 2fa55bb12a7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

spec-quick 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 5d 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 spec-quick — 68 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/kiro/spec-quick.md · 399 lines

How it starts

The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick Spec Generator

<background_information>

  • Mission: Execute all spec phases (init → requirements → design → tasks) in a single command
  • Success Criteria:
    • Interactive mode: User controls progression with approval prompts at each phase
    • Automatic mode: All phases execute without interruption when --auto flag provided
    • All generated specs maintain quality comparable to manual workflow </background_information>

If --auto flag is present in $ARGUMENTS, you are in AUTOMATIC MODE.

In Automatic Mode:

  • Execute ALL 4 phases in a continuous loop without stopping
  • Use TodoWrite to track progress (4 tasks: init, requirements, design, tasks)
  • Each phase completion updates TodoWrite and continues immediately
  • IGNORE any "Next Step" messages from Phase 2-4 (they are for standalone usage)
  • Stop ONLY after Phase 4 completes or if error occurs

Progress tracking with TodoWrite:

  • Phase 1 complete = 1/4 tasks done → Continue to Phase 2
  • Phase 2 complete = 2/4 tasks done → Continue to Phase 3
  • Phase 3 complete = 3/4 tasks done → Continue to Phase 4
  • Phase 4 complete = 4/4 tasks done → Output summary and exit

Core Task

Execute 4 spec phases sequentially. In automatic mode, execute all phases without stopping. In interactive mode, prompt user for approval between phases.

Execution Steps

Step 1: Parse Arguments and Initialize

Parse $ARGUMENTS:

  • If contains --auto: Automatic Mode (execute all 4 phases)
  • Otherwise: Interactive Mode (prompt at each phase)
  • Extract description (remove --auto flag if present)

Example:

"User profile with avatar upload --auto" → mode=automatic, description="User profile with avatar upload"
"User profile feature" → mode=interactive, description="User profile feature"

Create TodoWrite task list:

[
  {"content": "Initialize spec", "activeForm": "Initializing spec", "status": "pending"},
  {"content": "Generate requirements", "activeForm": "Generating requirements", "status": "pending"},
  {"content": "Generate design", "activeForm": "Generating design", "status": "pending"},
  {"content": "Generate tasks", "activeForm": "Generating tasks", "status": "pending"}
]

Read the full file on GitHub · 399 lines

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. 5d ago First seen · 399 lines · 8 tokens per session scan A 2fa55bb12a7c

Subscribe to this mod's changes

spec-quick is a command published in the GitHub repository j5ik2o/event-store-adapter-js (24 stars, last pushed 2d ago), licensed Apache-2.0. It adds 8 tokens to every session and 2,581 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to spec-quick, differing in 68 lines, and is treated as a copy.