A command that adds plain-language design explanation to an existing Z specification. Z is a formal way to describe a system's data, valid states, and operations.

Use it with a .tex specification and optional design documentation such as DESIGN.md or README.md. It adds sections covering the system, design choices, features, algorithms, and terminology.

A formal specification can be difficult to read on its own. This combines it with design documentation so the result explains both the rules and their purpose.

elaborate — Command for Claude Code by punt-labs

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.

Clone the repo

git clone --depth 1 https://github.com/punt-labs/z-spec

Made for: Claude Code.

Or install z-spec-dev, the plugin that ships this one along with the rest of its 42 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/punt-labs/z-spec/elaborate.svg)](https://agentmods.dev/commands/punt-labs/z-spec/elaborate)

Your own site

<a href="https://agentmods.dev/commands/punt-labs/z-spec/elaborate"><img src="https://agentmods.dev/badge/commands/punt-labs/z-spec/elaborate.svg" alt="Measured on agentmods" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,611 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01611
Opus 5	$0.00005	$0.00805
Sonnet 5	$0.00002	$0.00322
Haiku 4.5	$0.00001	$0.00161

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

Security

Grade A, and why

elaborate 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 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.

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

100% identical to elaborate-dev — 0 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.

plugin/commands/elaborate.md · 261 lines

How it starts

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

Elaborate Z Specification

You are enhancing a formal Z specification by combining it with design documentation to create a polished, readable artifact that serves both as formal specification and design documentation.

Input

Arguments: $ARGUMENTS

Parse arguments as:

First argument: path to Z specification (.tex file)
Second argument (optional): path to design documentation (defaults to DESIGN.md)

Process

1. Read the Specification

Read the Z specification file. Identify:

Basic types and their intended meaning
Free types (enumerations)
State schemas and their fields
Operations and their purpose
Any existing narrative text

2. Read Design Documentation

Search for design documentation in order:

Explicit path from arguments
DESIGN.md in project root
docs/DESIGN.md
README.md (extract design sections)

Extract relevant content:

System overview and purpose
Design philosophy and principles
Feature descriptions
Algorithm explanations
Domain terminology
Architectural decisions

3. Enhance the Specification

Transform the specification by adding:

Document Structure

\tableofcontents
\newpage

Introduction Section

System purpose from design docs
Design philosophy (bullet points)
Scope of specification (what is/isn't modeled)

Section Narratives

For each major section, add explanatory text:

Basic Types: Why these given sets? What do they represent?
Free Types: Domain meaning of each enumeration value
Constants: Why these values? What do they configure?
State Schemas:
- What does each field represent?
- Why these invariants matter?
- Semantic meaning (not just type)
Operations:
- When is this operation used?
- What triggers it?
- Connection to user actions or system events

Algorithm Explanations

Where operations implement algorithms from design docs:

Add tables summarizing rules (e.g., spaced repetition thresholds)
Note implementation details not captured in formal model
Reference design doc sections

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

7d ago First seen · 261 lines · 11 tokens per session scan A 6044640d845f

Subscribe to this mod's changes

elaborate is a command published in the GitHub repository punt-labs/z-spec (5 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 1,611 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to elaborate-dev, differing in 0 lines, and is treated as a copy.

LaTeX Writing and docs beta claude-code-plugin formal-methods z-notation z-notations

elaborate