spring-ai-rag-demo: Skill for Cursor

.cursor/skills/openspec-new-change/SKILL.md

openspec-new-change is a skill for Cursor from ly1836/spring-ai-rag-demo. It costs 40 tokens per session (658 once invoked), scanned A, a copy of openspec-new-change, Apache-2.0.

A command that starts a new OpenSpec change, where an OpenSpec change is a structured workspace for planning a feature or fix.

In plain words
What is it for?
Use it to turn a feature request or bug description into a named change directory and follow the default or requested workflow.
Why use it?
It gives a proposed change a consistent set of planning files and workflow before implementation begins.

Skill for Cursor

Written for Cursor: installed under .cursor/. Also seen: names the AskUserQuestion tool.

This is ly1836/spring-ai-rag-demo's own configuration. It tells Cursor how to work on spring-ai-rag-demo 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 spring-ai-rag-demo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ly1836/spring-ai-rag-demo. 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/ly1836/spring-ai-rag-demo/main/.cursor/skills/openspec-new-change/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ly1836/spring-ai-rag-demo

Made for: Cursor.

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 openspec-new-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/ly1836/spring-ai-rag-demo/openspec-new-change/github.svg)](https://agentmods.dev/skills/ly1836/spring-ai-rag-demo/openspec-new-change)
Your own site
<a href="https://agentmods.dev/skills/ly1836/spring-ai-rag-demo/openspec-new-change"><img src="https://agentmods.dev/badge/skills/ly1836/spring-ai-rag-demo/openspec-new-change/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 openspec-new-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/ly1836/spring-ai-rag-demo/openspec-new-change"><img src="https://agentmods.dev/badge/skills/ly1836/spring-ai-rag-demo/openspec-new-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 658 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 80% 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.00040 $0.00658
Opus 5 $0.00020 $0.00329
Sonnet 5 $0.00008 $0.00132
Haiku 4.5 $0.00004 $0.00066

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

Security

Grade A, and why

openspec-new-change 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 11d 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

80% identical to openspec-new-change — 12 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.

.cursor/skills/openspec-new-change/SKILL.md · 75 lines

What it actually says

Start a new change using the experimental artifact-driven approach.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

  1. If no clear input provided, ask what they want to build

    Use the AskUserQuestion tool (open-ended, no preset options) to ask:

    "What change do you want to work on? Describe what you want to build or fix."

    From their description, derive a kebab-case name (e.g., "add user authentication" → add-user-auth).

    IMPORTANT: Do NOT proceed without understanding what the user wants to build.

  2. Determine the workflow schema

    Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

    Use a different schema only if the user mentions:

    • A specific schema name → use --schema <name>
    • "show workflows" or "what workflows" → run openspec schemas --json and let them choose

    Otherwise: Omit --schema to use the default.

  3. Create the change directory

    openspec new change "<name>"
    

    Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.

  4. Show the artifact status

    openspec status --change "<name>"
    

    This shows which artifacts need to be created and which are ready (dependencies satisfied).

  5. Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".

    openspec instructions <first-artifact-id> --change "<name>"
    

    This outputs the template and context for creating the first artifact.

  6. STOP and wait for user direction

Output

After completing the steps, summarize:

  • Change name and location
  • Schema/workflow being used and its artifact sequence
  • Current status (0/N artifacts complete)
  • The template for the first artifact
  • Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."

Guardrails

  • Do NOT create any artifacts yet - just show the instructions
  • Do NOT advance beyond showing the first artifact template
  • If the name is invalid (not kebab-case), ask for a valid name
  • If a change with that name already exists, suggest continuing that change instead
  • Pass --schema if using a non-default workflow
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. 11d ago First seen · 75 lines · 40 tokens per session scan A 5daea20179a3

Subscribe to this mod's changes

openspec-new-change is a skill published in the GitHub repository ly1836/spring-ai-rag-demo (86 stars, last pushed 2d ago), licensed Apache-2.0. It adds 40 tokens to every session and 658 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to openspec-new-change, differing in 12 lines, and is treated as a copy.

Related

Other skills, from other repositories

docker-expert

Expert-level Docker containerization, image optimization, and container orchestration. Use this skill for building efficient Docker images, managing containers, and implementing Docker best practices.

personamanagmentlayer/pcl · 36 tokens

clawrouter

Hosted-gateway LLM router — save 84% on inference costs. A local proxy that forwards each request to the blockrun.ai gateway, which routes to the cheapest capable model across 78 models from OpenAI, Anthropic, Google, DeepSeek, xAI, Z.AI, and more. 7 free open-weight models included. Also exposes realtime market data…

BlockRunAI/ClawRouter · 222 tokens

surf

Use this skill — NOT browser or webfetch — for ALL Surf crypto-data calls. 83 endpoints at localhost:8402/v1/surf/ covering CEX/DEX markets, on-chain SQL over 80+ ClickHouse tables (Ethereum, Base, Arbitrum, BSC, TRON, HyperEVM, Tempo), 100M+ labeled wallets, prediction markets (Polymarket + Kalshi), social/CT…

BlockRunAI/ClawRouter · 148 tokens

phone

Verify phone numbers (carrier + SIM-swap fraud signals) and place AI-powered outbound voice calls via BlockRun's gateway (Twilio + Bland.ai). Trigger when the user asks to look up a number, check fraud risk, buy/rent a phone number, or place an AI voice call. Payment is automatic via x402 from the wallet.

BlockRunAI/ClawRouter · 72 tokens

imagegen

Generate or edit images via BlockRun's image API. Trigger when the user asks to generate, create, draw, make an image — or to edit, modify, change, or retouch an existing image.

BlockRunAI/ClawRouter · 45 tokens

polymarket-trading

Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrunpredexon data tools). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end flow.

BlockRunAI/ClawRouter · 76 tokens