beads-viz: Skill for Claude Code

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

openspec-onboard is a skill for Claude Code from pyros-projects/beads-viz. It costs 26 tokens per session (3,138 once invoked), scanned A, a copy of openspec-onboard, MIT.

A guided OpenSpec lesson that takes a developer through a complete change from planning to implementation and archiving. OpenSpec is a workflow for organizing code changes.

In plain words
What is it for?
Use it for a first OpenSpec workflow: choose a task, create planning documents, implement the change, and archive it.
Why use it?
It teaches the process while doing real work in the project, which helps someone learn by completing a full example.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is pyros-projects/beads-viz's own configuration. It tells Claude Code how to work on beads-viz 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 beads-viz configures →

Reuse

Borrowing it

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

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

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

.claude/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 pyros-projects/beads-viz (1 stars, last pushed 6mo 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

tradingview-mcp

AI Trading Intelligence — live prices, 30+ technical indicators, backtesting (6 strategies), walk-forward overfitting detection, trade logs, equity curves, licensed news sentiment (Marketaux), and multi-market screener. Supports stocks, crypto, ETFs, indices, Turkish (BIST), and Egyptian (EGX) markets.

atilaahmettaner/tradingview-mcp · 73 tokens

linkedin-mcp

Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server. Use only for an explicit LinkedIn request.

stickerdaniel/linkedin-mcp-server · 43 tokens

live-audit

Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…

Grinv/steam-games-mcp · 83 tokens

prompt-check

Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.

Grinv/steam-games-mcp · 54 tokens

dream

Consolidate and reorganize project memory (MEMORY.md) by invoking the dream-consolidator named subagent (Sonnet, pinned via the agent's model: frontmatter — NEVER pass a model: parameter yourself, it defeats the pin and runs the dream on expensive Opus). The subagent prompt is a CLOSED TEMPLATE: send its fields and…

wallneradam/project-mem-mcp · 144 tokens

project-memory

Maintain persistent project memory in MEMORY.md via MCP tools. SCOPE: codebase/architecture/conventions/gotchas + Recent Sessions of code work, in /MEMORY.md. DISTINCT from Claude Code's auto memory (/.claude/projects/ /memory/, holds user profile/preferences/feedback). Code-about → here; user-about → auto memory.…

wallneradam/project-mem-mcp · 297 tokens