Borrowing it
Nothing to install: this file belongs to sourjya/kiro-rails. 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/sourjya/kiro-rails/main/.claude/skills/spec-propose/SKILL.mdgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/skills/sourjya/kiro-rails/spec-propose)<a href="https://agentmods.dev/skills/sourjya/kiro-rails/spec-propose"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-propose/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/skills/sourjya/kiro-rails/spec-propose"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-propose.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.00038 | $0.00665 |
| Opus 5 | $0.00019 | $0.00332 |
| Sonnet 5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
spec-propose 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Propose Workflow
When the user wants to propose a new feature or change, create a structured spec folder BEFORE writing any code.
Steps
- Ask clarifying questions - understand scope, constraints, affected areas
- Create the spec folder at
.kiro/specs/<feature-name>/ - Generate all artifacts in order:
Folder Structure
.kiro/specs/<feature-name>/
├── proposal.md # Why this change exists
├── requirements.md # What the system should do
├── design.md # How to implement it
└── tasks.md # Checkbox-tracked implementation steps
proposal.md Template
# Proposal: <Feature Name>
## Problem Statement
What problem does this solve? Who is affected?
## Proposed Solution
High-level description of the approach.
## Scope
- **In scope:** what this change includes
- **Out of scope:** what this change explicitly excludes
## Success Criteria
How do we know this is done and working?
## Risks & Open Questions
- Risk 1: ...
- Question 1: ...
requirements.md Template
# Requirements: <Feature Name>
## Functional Requirements
### REQ-1: <Requirement Name>
**Description:** What the system must do.
**Acceptance Criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
### REQ-2: <Requirement Name>
...
## Non-Functional Requirements
- Performance: ...
- Security: ...
- Accessibility: ...
design.md Template
# Design: <Feature Name>
## Architecture
How this fits into the existing system.
## Key Decisions
| Decision | Rationale | Alternatives Considered |
|----------|-----------|------------------------|
| ... | ... | ... |
## Data Model Changes
Describe any schema/model changes.
## API Changes
Describe any endpoint additions/modifications.
## Dependencies
What this depends on, what depends on this.
tasks.md Template
Use the TDD template from .kiro/templates/tasks-template-tdd.md if available. Otherwise:
# Tasks: <Feature Name>
## Implementation Checklist
- [ ] Task 1: ...
- [ ] Task 2: ...
- [ ] Task 3: ...
## Testing
- [ ] Unit tests for ...
- [ ] Integration tests for ...
## Documentation
- [ ] Update relevant docs
- [ ] Add ADR if architectural decision was made
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.
- 9d ago First seen · 123 lines · 38 tokens per session scan A f00d40c29fa8
spec-propose is a skill published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 665 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…