opencode-obsidian: Skill for OpenCode

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

openspec-onboard is a skill for OpenCode from mtymek/opencode-obsidian. It costs 26 tokens per session (3,135 once invoked), scanned A, a copy of openspec-onboard, MIT.

A guided introduction to OpenSpec, a workflow for planning and implementing code changes through proposals, specifications, designs, tasks, and archiving.

In plain words
What is it for?
Use it to check whether OpenSpec is initialized and complete a first change from selecting a task through implementation and archiving.
Why use it?
It teaches the process by applying it to a real small change in the current codebase.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

This is mtymek/opencode-obsidian's own configuration. It tells OpenCode how to work on opencode-obsidian 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 opencode-obsidian configures →

About the project

OpenCode Obsidian is an Obsidian desktop plugin that embeds the OpenCode AI assistant in a vault's sidebar. It helps users summarize notes, refine writing, explore their knowledge base, and create structured outlines. The catalogue add-ons support workflows for this plugin and its OpenCode integration.

mtymek/opencode-obsidian · 1,156 stars · on GitHub

Reuse

Borrowing it

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

Made for: OpenCode.

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/mtymek/opencode-obsidian/openspec-onboard/github.svg)](https://agentmods.dev/skills/mtymek/opencode-obsidian/openspec-onboard)
Your own site
<a href="https://agentmods.dev/skills/mtymek/opencode-obsidian/openspec-onboard"><img src="https://agentmods.dev/badge/skills/mtymek/opencode-obsidian/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/mtymek/opencode-obsidian/openspec-onboard"><img src="https://agentmods.dev/badge/skills/mtymek/opencode-obsidian/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,135 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.03135
Opus 5.5 $0.00010 $0.01254
Sonnet 5.5 $0.00005 $0.00627
Haiku 4.5 $0.00003 $0.00314

Measured 2mo ago against content hash 96751574e71b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 — 151 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.

.opencode/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. 2mo ago First seen · 530 lines · 26 tokens per session scan A 96751574e71b

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens