mcp-server-template: Skill for Claude Code

.github/skills/openspec-onboard/SKILL.md

openspec-onboard is a skill for Claude Code, Codex from estebanjosse/mcp-server-template. It costs 26 tokens per session (3,138 once invoked), scanned A, a copy of openspec-onboard, MIT.

A guided lesson for using OpenSpec, a tool for planning and tracking code changes, through one complete task in your project.

In plain words
What is it for?
Finding a small improvement, writing its proposal, specifications, design, and task list, implementing it, and archiving the finished change.
Why use it?
It helps newcomers learn the process while doing real work, instead of reading instructions without context.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is estebanjosse/mcp-server-template's own configuration. It tells Claude Code and Codex how to work on mcp-server-template 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 mcp-server-template configures →

Reuse

Borrowing it

Nothing to install: this file belongs to estebanjosse/mcp-server-template. 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/estebanjosse/mcp-server-template/main/.github/skills/openspec-onboard/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/estebanjosse/mcp-server-template

Made for: Claude Code, Codex.

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-onboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/estebanjosse/mcp-server-template/openspec-onboard/github.svg)](https://agentmods.dev/skills/estebanjosse/mcp-server-template/openspec-onboard)
Your own site
<a href="https://agentmods.dev/skills/estebanjosse/mcp-server-template/openspec-onboard"><img src="https://agentmods.dev/badge/skills/estebanjosse/mcp-server-template/openspec-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 openspec-onboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/estebanjosse/mcp-server-template/openspec-onboard"><img src="https://agentmods.dev/badge/skills/estebanjosse/mcp-server-template/openspec-onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,138 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 78% 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.00026 $0.03138
Opus 5 $0.00013 $0.01569
Sonnet 5 $0.00005 $0.00628
Haiku 4.5 $0.00003 $0.00314

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

Security

Grade A, and why

openspec-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 8d 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

78% identical to openspec-onboard — 127 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.

.github/skills/openspec-onboard/SKILL.md · 530 lines

How it starts

The opening of the file, as written. The whole thing — 530 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 · 530 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. 8d ago First seen · 530 lines · 26 tokens per session scan A 058b568a7437

Subscribe to this mod's changes

openspec-onboard is a skill published in the GitHub repository estebanjosse/mcp-server-template (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 3,138 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to openspec-onboard, differing in 127 lines, and is treated as a copy.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

book-mirror

Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…

garrytan/gbrain · 138 tokens

miniapp

Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.

yc-software/qm · 25 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens

master-yinguang

A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.

xr843/Master-skill · 274 tokens