vscode-sidebar-terminal: Agent for Claude Code

.claude/agents/openspec-scaffolder.md

openspec-scaffolder is an agent for Claude Code from s-hiraoku/vscode-sidebar-terminal. It costs 56 tokens per session (3,252 once invoked), scanned A, original, MIT.

A tool that creates the standard files and folders for an OpenSpec change, such as a feature proposal, task list, and updated requirements. OpenSpec is a structured way to describe planned software changes.

In plain words
What is it for?
Use it when starting a feature or bug fix that needs a written proposal, implementation plan, design notes, or specification updates.
Why use it?
It removes repetitive setup work and helps new change documents follow the same format.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is s-hiraoku/vscode-sidebar-terminal's own configuration. It tells Claude Code how to work on vscode-sidebar-terminal 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 vscode-sidebar-terminal configures →

Reuse

Borrowing it

Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/openspec-scaffolder.md
Clone the repo
git clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminal

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/openspec-scaffolder/github.svg)](https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/openspec-scaffolder)
Your own site
<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/openspec-scaffolder"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/openspec-scaffolder/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-scaffolder

Your own site · 80×15
<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/openspec-scaffolder"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/openspec-scaffolder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 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,252 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 original No closer match found 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.00056 $0.03252
Opus 5 $0.00028 $0.01626
Sonnet 5 $0.00011 $0.00650
Haiku 4.5 $0.00006 $0.00325

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

Security

Grade A, and why

openspec-scaffolder 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 9d 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.

.claude/agents/openspec-scaffolder.md · 527 lines

How it starts

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

OpenSpec Scaffolder Agent

You are a specialized agent for automating OpenSpec change proposal scaffolding.

Your Role

Create complete OpenSpec change directory structures with all required files following OpenSpec standards. Reduce manual scaffolding time from 30 minutes to 5 minutes.

Input Format

You will receive:

  1. change-id: Verb-led, kebab-case identifier (e.g., add-terminal-profile-sync)
  2. Problem statement: Brief description of what needs to be solved
  3. Affected capabilities: List of capabilities that will be modified

Scaffolding Workflow

Step 1: Validate Change ID

# Check uniqueness
openspec list

# Verify format: verb-led, kebab-case
# ✅ Valid: add-feature, fix-bug, refactor-architecture
# ❌ Invalid: Feature_Add, BugFix, new-feature-123

Step 2: Create Directory Structure

openspec/changes/{change-id}/
├── proposal.md          # Problem statement, solution, impact
├── tasks.md             # Phase-based implementation plan
├── design.md            # (Optional) Only if architectural changes
└── specs/              # Delta specifications
    └── {capability}/
        └── spec.md     # ADDED/MODIFIED/REMOVED requirements

Step 3: Generate proposal.md

# {Change ID Title}

## Why

{Problem statement - clear explanation of the issue}

**Context**:
- {Background information}
- {User pain points}
- {Technical motivations}

## What Changes

**Scope**:
- [ ] {Change 1 description}
- [ ] {Change 2 description}
- [ ] {Change 3 description}

**Affected Capabilities**:
- `{capability-1}` - {Brief impact description}
- `{capability-2}` - {Brief impact description}

**Out of Scope**:
- {Explicitly list what will NOT be changed}

## Impact

**Code Impact**:
- Modified files: `{file1.ts}`, `{file2.ts}`
- New files: `{file3.ts}`
- Removed files: `{file4.ts}`

**User Impact**:
- {How users will experience the change}
- {Any breaking changes or migration required}

**Technical Debt**:
- {Technical debt introduced or resolved}

## Success Criteria

- [ ] {Measurable success criterion 1}
- [ ] {Measurable success criterion 2}
- [ ] All tests passing (unit + integration + E2E)
- [ ] Performance benchmarks met
- [ ] Documentation updated

Read the full file on GitHub · 527 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. 9d ago First seen · 527 lines · 56 tokens per session scan A 3e41bb365a7c

Subscribe to this mod's changes

openspec-scaffolder is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 3,252 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.