versioning-constitutions

versioning-constitutions is a skill for Claude Code from arittr/spectacular. It costs 45 tokens per session (1,848 once invoked), scanned B, original, MIT.

A workflow for recording changes to a project's foundational architecture as new, immutable constitution versions instead of rewriting past rules.

In plain words
What is it for?
Use it when mandatory architecture or technology rules change, to organize the new version, update the active link, and document the change.
Why use it?
It preserves the history of important changes such as technology migrations, new required patterns, or altered architectural boundaries.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the spectacular plugin — 14 skills, 5 commands, 1 hook shipped together

Good fit Use it when mandatory architecture or technology rules change, to organize the…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arittr/spectacular/versioning-constitutions
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 arittr/spectacular --skill versioning-constitutions
Clone the repo
git clone --depth 1 https://github.com/arittr/spectacular

Made for: Claude Code.

Or install spectacular, the plugin that ships this one along with the rest of its 14 skills, 5 commands, 1 hook.

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 versioning-constitutions

README.md
[![agentmods](https://agentmods.dev/badge/skills/arittr/spectacular/versioning-constitutions.svg)](https://agentmods.dev/skills/arittr/spectacular/versioning-constitutions)
Your own site
<a href="https://agentmods.dev/skills/arittr/spectacular/versioning-constitutions"><img src="https://agentmods.dev/badge/skills/arittr/spectacular/versioning-constitutions.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,848 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00045 $0.01848
Opus 5 $0.00023 $0.00924
Sonnet 5 $0.00009 $0.00370
Haiku 4.5 $0.00005 $0.00185

Measured 7d ago against content hash ba59f8fb9b01, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

versioning-constitutions scanned grade B with 1 finding 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 7d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

grep -r "@docs/constitutions/current" .claude/
skills/versioning-constitutions/SKILL.md · 225 lines

How it starts

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

Versioning Constitutions

Core Principle

Constitution versions are immutable snapshots of architectural truth.

When foundational rules change (patterns, tech stack, architecture), create a new version rather than editing in place. This preserves history, enables rollback, and makes changes explicit.

When to Use This Skill

ALWAYS create a new version when:

  • Adding a new mandatory pattern (e.g., adopting effect-ts for error handling)
  • Removing OR relaxing a mandatory pattern (e.g., making next-safe-action optional)
  • Changing tech stack (e.g., migrating from Prisma to Drizzle)
  • Updating architectural boundaries (e.g., adding new layer)
  • Deprecating rules that are no longer valid
  • Major library version changes with breaking patterns (e.g., Next.js 15 → 16)

CRITICAL: Removing or relaxing a mandatory pattern ALWAYS requires a new version, even if existing code would still work. "Non-breaking" is not sufficient - any change to mandatory patterns needs versioning for audit trail.

Do NOT use for:

  • Fixing typos or clarifying existing rules (edit current version directly)
  • Adding examples to existing patterns (edit current version directly)
  • Project-specific implementation details (those go in specs/)

Test for Constitutionality:

Before adding content to constitution, ask: "If we violate this rule, does the architecture break?"

  • ✅ Constitutional: "Must use next-safe-action" → violating breaks type safety & validation
  • ❌ Not constitutional: "Forms should have wrapper, fields, button" → violating just looks different

Constitution = Architectural rules. Specs = Implementation patterns.

Process

Step 1: Determine Version Number

Read docs/constitutions/current/meta.md to get current version.

Version increment rules:

  • Increment by 1 (v1 → v2, v2 → v3)
  • No semantic versioning (major.minor.patch)
  • Sequential only

Step 2: Create New Version Directory

# Create new version directory
mkdir -p docs/constitutions/v{N}

# Copy structure from current
cp docs/constitutions/current/*.md docs/constitutions/v{N}/

Read the full file on GitHub · 225 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago First seen · 225 lines · 45 tokens per session scan B ba59f8fb9b01

Subscribe to this mod's changes

versioning-constitutions is a skill published in the GitHub repository arittr/spectacular (20 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 1,848 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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