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.
npx agentmods add skills/tim-mccrimmon/structured-context-spec/versionnpx skills add tim-mccrimmon/structured-context-spec --skill versiongit clone --depth 1 https://github.com/tim-mccrimmon/structured-context-specWrote 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.
[](https://agentmods.dev/skills/tim-mccrimmon/structured-context-spec/version)<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="Measured on agentmods" height="20"></a>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 | $0.00022 | $0.01597 |
| Opus 5 | $0.00011 | $0.00798 |
| Sonnet 5 | $0.00004 | $0.00319 |
| Haiku 4.5 | $0.00002 | $0.00160 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 204 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: Concern 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 concern bundles first (they have no imports)
- Update project bundle to reference versioned concerns
- 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:
provenance:
versioned_by: "<User>"
versioned_at: "<ISO timestamp>"
version_rationale: "<Why this version>"
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.
- 3d ago First seen · 204 lines · 22 tokens per session scan A 8b66a3670550
version is a skill published in the GitHub repository tim-mccrimmon/structured-context-spec (19 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,597 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
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…
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
rpce-release
Build or publish RepoPrompt CE release artifacts using the repository release scripts and GitHub workflows.
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.
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.