SharpPad: Command for Claude Code

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

spec-init is a command for Claude Code from gaoconggit/SharpPad. It costs 10 tokens per session (617 once invoked), scanned A, a copy of spec-init, MIT.

A command that starts a new project specification from a written project description. It creates a uniquely named folder with initial metadata and a requirements document.

In plain words
What is it for?
Use it to begin a structured feature proposal in a project that uses the .kiro/specs/ directory.
Why use it?
It removes the manual setup needed before documenting a feature or project, while avoiding a name clash with an existing specification.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

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

Reuse

Borrowing it

Nothing to install: this file belongs to gaoconggit/SharpPad. 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/gaoconggit/SharpPad/main/.claude/commands/kiro/spec-init.md
Clone the repo
git clone --depth 1 https://github.com/gaoconggit/SharpPad

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-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-init/github.svg)](https://agentmods.dev/commands/gaoconggit/sharppad/spec-init)
Your own site
<a href="https://agentmods.dev/commands/gaoconggit/sharppad/spec-init"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-init/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 spec-init

Your own site · 80×15
<a href="https://agentmods.dev/commands/gaoconggit/sharppad/spec-init"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/spec-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 617 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 100% 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.00010 $0.00617
Opus 5.5 $0.00004 $0.00247
Sonnet 5.5 $0.00002 $0.00123
Haiku 4.5 $0.00001 $0.00062

Measured 13d ago against content hash ed22f5aebe05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-init 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 13d 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

100% identical to spec-init — 3 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-init.md · 87 lines

How it starts

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

Spec Initialization

Initialize a new specification based on the provided project description:

Project Description: $ARGUMENTS

Task: Initialize Specification Structure

SCOPE: This command initializes the directory structure and metadata based on the detailed project description provided.

1. Generate Feature Name

Create a concise, descriptive feature name from the project description ($ARGUMENTS). Check existing .kiro/specs/ directory to ensure the generated feature name is unique. If a conflict exists, append a number suffix (e.g., feature-name-2).

2. Create Spec Directory

Create .kiro/specs/[generated-feature-name]/ directory with:

  • spec.json - Metadata and approval tracking
  • requirements.md - Lightweight template with project description

Note: design.md and tasks.md will be created by their respective commands during the development process.

3. Initialize spec.json Metadata

Create initial metadata with approval tracking:

{
  "feature_name": "[generated-feature-name]",
  "created_at": "current_timestamp",
  "updated_at": "current_timestamp",
  "language": "ja",
  "phase": "initialized",
  "approvals": {
    "requirements": {
      "generated": false,
      "approved": false
    },
    "design": {
      "generated": false,
      "approved": false
    },
    "tasks": {
      "generated": false,
      "approved": false
    }
  },
  "ready_for_implementation": false
}

4. Create Requirements Template

Create requirements.md with project description:

# Requirements Document

## Project Description (Input)
$ARGUMENTS

## Requirements
<!-- Will be generated in /kiro:spec-requirements phase -->

5. Update CLAUDE.md Reference

Add the new spec to the active specifications list with the generated feature name and a brief description.

Next Steps After Initialization

Follow the strict spec-driven development workflow:

  1. /kiro:spec-requirements <feature-name> - Create and generate requirements.md
  2. /kiro:spec-design <feature-name> - Create and generate design.md (requires approved requirements)
  3. /kiro:spec-tasks <feature-name> - Create and generate tasks.md (requires approved design)

Read the full file on GitHub · 87 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. 13d ago First seen · 87 lines · 10 tokens per session scan A ed22f5aebe05

Subscribe to this mod's changes

spec-init is a command published in the GitHub repository gaoconggit/SharpPad (83 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 617 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to spec-init, differing in 3 lines, and is treated as a copy.