memoir: Skill for Claude Code

.agents/skills/source-command-opsx-onboard/SKILL.md

source-command-opsx-onboard is a skill for Claude Code, Codex from killin0415/memoir. It costs 22 tokens per session (3,353 once invoked), scanned A, a copy of openspec-onboard, MIT.

A guided lesson through a complete OpenSpec software-change workflow, from choosing a task to archiving the result.

In plain words
What is it for?
Use it for a first end-to-end OpenSpec cycle, including checking whether the OpenSpec command-line tool is installed.
Why use it?
It helps someone learn OpenSpec by doing real work while explaining proposals, specifications, design, tasks, and implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

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

Reuse

Borrowing it

Nothing to install: this file belongs to killin0415/memoir. 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/killin0415/memoir/main/.agents/skills/source-command-opsx-onboard/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/killin0415/memoir

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 source-command-opsx-onboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/killin0415/memoir/source-command-opsx-onboard/github.svg)](https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-onboard)
Your own site
<a href="https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-onboard"><img src="https://agentmods.dev/badge/skills/killin0415/memoir/source-command-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 source-command-opsx-onboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-onboard"><img src="https://agentmods.dev/badge/skills/killin0415/memoir/source-command-opsx-onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,353 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 77% 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.00022 $0.03353
Opus 5.5 $0.00009 $0.01341
Sonnet 5.5 $0.00004 $0.00671
Haiku 4.5 $0.00002 $0.00335

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

Security

Grade A, and why

source-command-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 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.

Origin

This is a copy

77% identical to openspec-onboard — 156 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.

.agents/skills/source-command-opsx-onboard/SKILL.md · 555 lines

How it starts

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

source-command-opsx-onboard

Use this skill when the user asks to run the migrated source command opsx-onboard.

Command Template

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 the OpenSpec CLI is installed:

# Unix/macOS
openspec --version 2>&1 || echo "CLI_NOT_INSTALLED"
# Windows (PowerShell)
# if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" }

If CLI not installed:

OpenSpec CLI is not installed. Install it first, then come back to /opsx:onboard.

Stop here if not installed.


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:

# Unix/macOS
git log --oneline -10 2>/dev/null || echo "No git history"
# Windows (PowerShell)
# git log --oneline -10 2>$null; if ($LASTEXITCODE -ne 0) { echo "No git history" }

Read the full file on GitHub · 555 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 First seen · 555 lines · 22 tokens per session scan A 6680a06dab64

Subscribe to this mod's changes

source-command-opsx-onboard is a skill published in the GitHub repository killin0415/memoir (5 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 3,353 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 77% identical to openspec-onboard, differing in 156 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

exam-forecast

Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.

anthropics/claude-for-legal · 73 tokens

lean-formalize

Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…

wanshuiyin/Auto-claude-code-research-in-sleep · 81 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