continue-framework: Skill for Claude Code

.claude/skills/api-spec/SKILL.md

api-spec is a skill for Claude Code from rakovi4/continue-framework. It costs 29 tokens per session (903 once invoked), scanned A, original, MIT.

A skill for generating OpenAPI 3.0.3 descriptions of the API endpoints needed by a product story. OpenAPI is a standard format for documenting how software systems communicate over an API.

In plain words
What is it for?
Use it to select a story from product documents and create the minimum frontend API specification, including request and response needs.
Why use it?
It helps turn a feature story into a small, focused API design instead of adding unnecessary endpoints.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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

Reuse

Borrowing it

Nothing to install: this file belongs to rakovi4/continue-framework. 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/rakovi4/continue-framework/main/.claude/skills/api-spec/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rakovi4/continue-framework

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/rakovi4/continue-framework/api-spec/github.svg)](https://agentmods.dev/skills/rakovi4/continue-framework/api-spec)
Your own site
<a href="https://agentmods.dev/skills/rakovi4/continue-framework/api-spec"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/api-spec/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 api-spec

Your own site · 80×15
<a href="https://agentmods.dev/skills/rakovi4/continue-framework/api-spec"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/api-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 903 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00029 $0.00903
Opus 5.5 $0.00012 $0.00361
Sonnet 5.5 $0.00006 $0.00181
Haiku 4.5 $0.00003 $0.00090

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

Security

Grade A, and why

api-spec 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 1mo 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.

.claude/skills/api-spec/SKILL.md · 80 lines

How it starts

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

Generate API Specification

Generate OpenAPI 3.0.3 specifications for frontend endpoints in a story.

Usage

/api-spec "Story name"
/api-spec 5                    # By MVP story number
/api-spec                      # Interactive selection

MVP Mindset

Generate the MINIMUM viable API, not the complete API.

  • Prefer fewer endpoints - consolidate where possible
  • No health/status endpoints (infrastructure, not features)
  • No separate replace endpoints (use PUT on same resource)
  • No separate "get current state" if POST response returns it
  • When in doubt, leave it out

Workflow

Phase 1: Context & Story Selection

  1. Read context files:

    • ProductSpecification/BriefProductDescription.md
    • ProductSpecification/stories.md
  2. Parse user input to find target story (by name, number, or interactive)

  3. Read the target story's folder — stories/NN-story-name/ first, then stories/done/NN-story-name/ (.claude/rules/workflow.md, "Resolving a story folder"), since an unresolved archived folder reads exactly like a story with no interview: NN_StoryName.md (specification), mockups/ (UI mockups — the fields each screen needs), interview.md if it exists (authoritative source for API details)

  4. Read what the areas this story touches already expose — the acceptance tests of those areas, for their request/response shapes, status codes and Statements. Never sweep stories/*/mockups/ or stories/*/interview.md to reconstruct it (.claude/rules/workflow.md, "Where the Current State Lives"). Only enabled tests count as shipped — one still carrying its disable/skip marker is a pending increment, not a live endpoint. Where the suite is silent about an area, read that area's controllers and say what you found — silence is not evidence that no endpoint exists. In a repo with no acceptance suite yet, say so explicitly and fall back to the story folders. Open an earlier story's interview.md or decisions/*-decision.md only for a named precedent — the rule behind an existing response shape — resolving it under stories/ or stories/done/, since the story that set the shape has usually closed (.claude/rules/workflow.md, "Resolving a story folder")

Read the full file on GitHub · 80 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. 1mo ago Changed · +18 lines c1c8efb4d47f
  2. 2mo ago First seen · 62 lines · 29 tokens per session scan A 686aa7157442

Subscribe to this mod's changes

api-spec is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 29 tokens to every session and 903 once invoked, about $0.0001 per session on Opus 5.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-30.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

dev-runtime

How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…

langwatch/langwatch · 172 tokens

api-design

Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…

ericrisco/rsc-harness · 105 tokens