swift-index: Command for Claude Code

.cursor/commands/opsx-onboard.md

/opsx-onboard is a command for Claude Code, Cursor from alexey1312/swift-index. It costs 20 tokens per session (3,105 once invoked), scanned A, a copy of OPSX: Onboard, MIT.

A guided command that teaches the OpenSpec workflow, a process for turning a coding idea into proposals, specifications, design, tasks, implementation, and an archived change.

In plain words
What is it for?
Use it to check OpenSpec setup, find a suitable task, create the required planning documents, implement the work, and archive the completed change.
Why use it?
It helps a new user learn the complete process by carrying out a real, small change in the current codebase.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is alexey1312/swift-index's own configuration. It tells Claude Code and Cursor how to work on swift-index 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 swift-index configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alexey1312/swift-index. 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/alexey1312/swift-index/main/.cursor/commands/opsx-onboard.md
Clone the repo
git clone --depth 1 https://github.com/alexey1312/swift-index

Made for: Claude Code, 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 /opsx-onboard

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexey1312/swift-index/opsx-onboard/github.svg)](https://agentmods.dev/commands/alexey1312/swift-index/opsx-onboard)
Your own site
<a href="https://agentmods.dev/commands/alexey1312/swift-index/opsx-onboard"><img src="https://agentmods.dev/badge/commands/alexey1312/swift-index/opsx-onboard/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 /opsx-onboard

Your own site · 80×15
<a href="https://agentmods.dev/commands/alexey1312/swift-index/opsx-onboard"><img src="https://agentmods.dev/badge/commands/alexey1312/swift-index/opsx-onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,105 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 91% 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.00020 $0.03105
Opus 5 $0.00010 $0.01553
Sonnet 5 $0.00004 $0.00621
Haiku 4.5 $0.00002 $0.00311

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

Security

Grade A, and why

/opsx-onboard 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 10d 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

91% identical to OPSX: Onboard — 6 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/commands/opsx-onboard.md · 526 lines

How it starts

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

Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.


Preflight

Before starting, check if OpenSpec is initialized:

openspec status --json 2>&1 || echo "NOT_INITIALIZED"

If not initialized:

OpenSpec isn't set up in this project yet. Run openspec init first, then come back to /opsx:onboard.

Stop here if not initialized.


Phase 1: Welcome

Display:

## Welcome to OpenSpec!

I'll walk you through a complete change cycle—from idea to implementation—using a real task in your codebase. Along the way, you'll learn the workflow by doing it.

**What we'll do:**
1. Pick a small, real task in your codebase
2. Explore the problem briefly
3. Create a change (the container for our work)
4. Build the artifacts: proposal → specs → design → tasks
5. Implement the tasks
6. Archive the completed change

**Time:** ~15-20 minutes

Let's start by finding something to work on.

Phase 2: Task Selection

Codebase Analysis

Scan the codebase for small improvement opportunities. Look for:

  1. TODO/FIXME comments - Search for TODO, FIXME, HACK, XXX in code files
  2. Missing error handling - catch blocks that swallow errors, risky operations without try-catch
  3. Functions without tests - Cross-reference src/ with test directories
  4. Type issues - any types in TypeScript files (: any, as any)
  5. Debug artifacts - console.log, console.debug, debugger statements in non-debug code
  6. Missing validation - User input handlers without validation

Also check recent git activity:

git log --oneline -10 2>/dev/null || echo "No git history"

Present Suggestions

From your analysis, present 3-4 specific suggestions:

## Task Suggestions

Based on scanning your codebase, here are some good starter tasks:

**1. [Most promising task]**
   Location: `src/path/to/file.ts:42`
   Scope: ~1-2 files, ~20-30 lines
   Why it's good: [brief reason]

**2. [Second task]**
   Location: `src/another/file.ts`
   Scope: ~1 file, ~15 lines
   Why it's good: [brief reason]

**3. [Third task]**
   Location: [location]
   Scope: [estimate]
   Why it's good: [brief reason]

**4. Something else?**
   Tell me what you'd like to work on.

Which task interests you? (Pick a number or describe your own)

Read the full file on GitHub · 526 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. 10d ago First seen · 526 lines · 20 tokens per session scan A 7141f1f9c279

Subscribe to this mod's changes

/opsx-onboard is a command published in the GitHub repository alexey1312/swift-index (5 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 3,105 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to OPSX: Onboard, differing in 6 lines, and is treated as a copy.