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.
curl -O https://raw.githubusercontent.com/gaoconggit/SharpPad/main/.claude/commands/kiro/spec-init.mdgit clone --depth 1 https://github.com/gaoconggit/SharpPadWrote 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/gaoconggit/sharppad/spec-init)<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.
<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>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.00010 | $0.00617 |
| Opus 5.5 | $0.00004 | $0.00247 |
| Sonnet 5.5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00062 |
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.
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.
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 trackingrequirements.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:
/kiro:spec-requirements <feature-name>- Create and generate requirements.md/kiro:spec-design <feature-name>- Create and generate design.md (requires approved requirements)/kiro:spec-tasks <feature-name>- Create and generate tasks.md (requires approved design)
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.
- 13d ago First seen · 87 lines · 10 tokens per session scan A ed22f5aebe05
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.
Other commands, from other repositories
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
project-principles
Define your project's non-negotiable principles, commitments, and boundaries.
fast
⚡⚡⚡ Quickly bootstrap a new project automatically.
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
shortlist
Select and prioritize MVP features from an existing backlog.