A user-invoked workflow for assigning semantic versions to bundles of structured project context. Semantic versioning uses major, minor, and patch numbers to describe the size of changes.

Use it to validate bundles, choose version numbers, update version files, and integrate the result with Git after confirmation.

It helps record compatible and breaking changes while keeping released bundles unchanged.

version — Skill for Claude Code by tim-mccrimmon

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add tim-mccrimmon/structured-context-spec --skill version

Clone the repo

git clone --depth 1 https://github.com/tim-mccrimmon/structured-context-spec

Made for: Claude Code.

Or install scs-team, the plugin that ships this one along with the rest of its 7 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tim-mccrimmon/structured-context-spec/version/github.svg)](https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/version)

Your own site

<a href="https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/version"><img src="https://agentmods.dev/badge/skills/tim-mccrimmon/structured-context-spec/version/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/version"><img src="https://agentmods.dev/badge/skills/tim-mccrimmon/structured-context-spec/version.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 1,646 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.

Model	Per session	Once invoked
Fable 5.1	$0.00022	$0.01646
Opus 5.5	$0.00009	$0.00658
Sonnet 5.5	$0.00004	$0.00329
Haiku 4.5	$0.00002	$0.00165

Measured 22d ago against content hash d5d3c924c0f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

version 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 22d 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.

plugins/scs-team/skills/version/SKILL.md · 206 lines

How it starts

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

Invocation Rules

User-initiated only: Do NOT invoke this skill unless the user explicitly runs /scs-team:version. Never auto-invoke based on project state or conversation context.
Confirm before writing: Present the full versioning plan (which bundles, which version numbers, git actions) and get explicit user confirmation before modifying any files.

SCS Team Version - Lock Context with Semantic Version

You are helping the user version their structured context, locking it for use.

Versioning Philosophy

Version bottom-up: Concept bundles first, then domain/project bundles.

Semantic versioning:

MAJOR (1.0.0 → 2.0.0): Breaking changes, removed SCDs, changed structure
MINOR (1.0.0 → 1.1.0): New SCDs added, new content, backward compatible
PATCH (1.0.0 → 1.0.1): Fixes, clarifications, no structural changes

Immutable once versioned: A versioned bundle should not change. Create a new version instead.

Your Process

Step 1: Pre-Version Check

Before versioning:

Run validation checks (like /scs-team:validate)
Identify what's currently DRAFT
Check for unresolved TBD items
Verify no broken references

If there are blocking issues, stop and report them.

Step 2: Determine Version Strategy

Ask the user:

Is this the first version? → Suggest 1.0.0
Are there breaking changes? → MAJOR bump
New content added? → MINOR bump
Just fixes? → PATCH bump

Step 3: Version Bottom-Up

Order of operations:

Version concept bundles first (they have no imports)
Update project bundle to reference versioned concepts
Version project bundle last

Step 4: Update Files

For each bundle being versioned:

# Before
version: "DRAFT"

# After
version: "1.0.0"

For SCDs in versioned bundles:

# Before
version: "DRAFT"

# After
version: "1.0.0"

Update provenance. Field names must match the schema's required fields for a non-DRAFT version (RFC-0001, Provenance and approval) - version_approved_by and version_approved_at, not versioned_by/versioned_at:

provenance:
  version_approved_by: "<User>"
  version_approved_at: "<ISO timestamp>"
  rationale: "<Why this version>"

Read the full file on GitHub · 206 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.

22d ago Changed · +2 lines d5d3c924c0f2
1mo ago First seen · 204 lines · 22 tokens per session scan A 8b66a3670550

Subscribe to this mod's changes

version is a skill published in the GitHub repository tim-mccrimmon/structured-context-spec (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,646 once invoked, about $0.0001 per session on Opus 5.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-08-30.

Git and workflow Releases agent-context ai context context-engineering context-management structured-context

changelog-conventions

How The Lossless Group writes and structures changelog/ entries across all repos (projects, true monorepos, pseudomonorepos). Use whenever shipping or pushing a coherent chunk of work, when scaffolding a new repo's changelog/ directory, when authoring a product release message, when the user says "log this", "write a…

lossless-group/lossless-agent-skills · 191 tokens

gsd-complete-milestone

Archive completed milestone and prepare for next version.

open-gsd/gsd-core · 16 tokens

changelog

Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.

ratel-ai/ratel · 74 tokens

version