mozaiks: Skill for Claude Code

.agents/skills/build-sequence-change/SKILL.md

build-sequence-change is a skill for Claude Code from BlocUnited-LLC/mozaiks. It costs 29 tokens per session (423 once invoked), scanned A, original, MIT.

A workflow-sequence review and implementation guide for Extension Registry build journeys. It distinguishes cross-workflow sequences, user transitions, routing inside a workflow, and external entry points.

In plain words
What is it for?
Use it to inspect or modify workflow sequences, transitions, entry points, routing files, and the composition of build or revision journeys.
Why use it?
It helps prevent changes from breaking how build steps connect across workflows or conflict with another open change.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is BlocUnited-LLC/mozaiks's own configuration. It tells Claude Code how to work on mozaiks 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 mozaiks configures →

Reuse

Borrowing it

Nothing to install: this file belongs to BlocUnited-LLC/mozaiks. 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/BlocUnited-LLC/mozaiks/main/.agents/skills/build-sequence-change/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/BlocUnited-LLC/mozaiks

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 build-sequence-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/build-sequence-change/github.svg)](https://agentmods.dev/skills/blocunited-llc/mozaiks/build-sequence-change)
Your own site
<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/build-sequence-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/build-sequence-change/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 build-sequence-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/build-sequence-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/build-sequence-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 423 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00029 $0.00423
Opus 5 $0.00015 $0.00211
Sonnet 5 $0.00006 $0.00085
Haiku 4.5 $0.00003 $0.00042

Measured 8d ago against content hash 5932faf454bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

build-sequence-change 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 8d 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.

.agents/skills/build-sequence-change/SKILL.md · 50 lines

What it actually says

Before starting: git fetch origin && gh pr list --state open && git log origin/main --oneline -3 — if another agent has an open PR touching the same files you need, wait for it to merge or branch off it instead of main.

Use this skill when a change touches build journey composition.

Inspect first:

  • factory_app/workflows/extended_orchestration/extension_registry.json
  • docs/architecture/workflows/workflow-routing-transitions.md
  • docs/architecture/orchestration-and-decomposition.md
  • docs/architecture/workflows/control-plane-harness-architecture.md when sequence ids are referenced by control-plane routes
  • the orchestrator.yaml and transition_graph.yaml files of each affected workflow

Keep these distinct:

  • workflow_sequence / workflow_sequences[] = cross-workflow build or revision journey
  • transitions[] = user choice or deterministic context seed
  • transition_graph.yaml = agent routing inside one workflow
  • entrypoints[] = external route entry into a sequence or transition

Current build truth:

  • build is workflow_sequence-driven
  • ValueEngine owns concept and value decomposition
  • ThemeCapture owns brand and theme capture
  • DesignDocs owns design intent
  • AgentGenerator owns workflow bundle generation
  • AppGenerator owns final app-bundle generation
  • ExistingAppDiscovery is brownfield discovery, not the default greenfield build path

If a workflow_sequence id changes, update control_plane.yaml, docs, and tests that reference it.

Return:

  1. workflow_sequence affected
  2. workflows affected
  3. transitions affected
  4. entrypoints affected
  5. downstream artifacts affected
  6. tests required/run
  7. rollback risk
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. 8d ago First seen · 50 lines · 29 tokens per session scan A 5932faf454bb

Subscribe to this mod's changes

build-sequence-change is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 423 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.

Related

Other skills, from other repositories

building-pydantic-ai-agents

Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…

pydantic/pydantic-ai · 85 tokens

migrating-langchain-to-pydantic-ai

Migrate Python LangChain or LangGraph applications to Pydantic AI. Use for LangChain agents, chains, LCEL, or direct LangGraph graphs, persistence, interrupts, and streaming. Do not use for migrations centered on createdeepagent or Deep Agents harness features.

pydantic/pydantic-ai · 69 tokens

agentfield-use

Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …

Agent-Field/agentfield · 259 tokens

agentfield

Design and ship a multi-agent system on AgentField. Use when the user asks to build, scaffold, design, or run an agent, reasoner network, multi-agent backend, or 'an agent that does X' — whenever the work would otherwise be a single LLM call or a flat LangChain/CrewAI/AutoGen chain. The skill produces composite…

Agent-Field/agentfield · 127 tokens

agentfield-personal

Build and install a personal AI agent on this machine's AgentField: real source in /agentfield-agents, packaged with agentfield-package.yaml, installed with af install, started with af run, registered on the local control plane, and visible in AgentField Desktop with a keys form and an auto-start toggle. Use when the…

Agent-Field/agentfield · 134 tokens

hephaestus-network

Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.

agentlas-ai/Agentlas-OS · 75 tokens