What is factory-build-workflow-change?

A guide for changing the factory build workflow system, which coordinates workflows that create applications and connect their build stages. It covers routing, transitions, entry points, generated artifacts, and build lifecycle integration.

Use it when changing workflow sequences, build routing, AppGenerator, AgentGenerator, ExistingAppDiscovery, artifact ownership, lifecycle hooks, or shared workflow tools.

It helps preserve correct handoffs between application discovery, agent generation, application generation, and other build stages.

How BlocUnited-LLC/mozaiks configures Claude Code

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/factory-build-workflow-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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/factory-build-workflow-change/github.svg)](https://agentmods.dev/skills/blocunited-llc/mozaiks/factory-build-workflow-change)

Your own site

<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/factory-build-workflow-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/factory-build-workflow-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/factory-build-workflow-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/factory-build-workflow-change.svg" alt="Reviewed on agentmods" width="80" 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 2,452 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.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.02452
Opus 5	$0.00023	$0.01226
Sonnet 5	$0.00009	$0.00490
Haiku 4.5	$0.00005	$0.00245

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

Security

Grade A, and why

factory-build-workflow-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 10d 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/factory-build-workflow-change/SKILL.md · 180 lines

How it starts

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

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 the factory build workflow system.

Typical triggers:

factory_app/workflows/extended_orchestration/extension_registry.json
workflow_sequences[], transitions[], or entrypoints[]
build journey sequencing or branch routing
factory_app/workflows/AppGenerator/**
factory_app/workflows/AgentGenerator/**
factory_app/workflows/ExistingAppDiscovery/**
build lifecycle hooks in factory_app/workflows/_shared/platform/build_lifecycle.py
artifact routing, generated artifact ownership, or workflow integration contracts
shared workflow tools, hooks, reusable workflow UI, or cross-workflow build glue
build control-plane or refinement integration that references workflow_sequence

Inspect first:

ARCHITECTURE.md
AGENTS.md
CLAUDE.md
.claude/rules/factory-build-workflows.md
.claude/rules/build-refinement-truth.md
.claude/rules/testing.md
factory_app/workflows/extended_orchestration/extension_registry.json
docs/architecture/workflows/workflow-routing-transitions.md
docs/architecture/orchestration-and-decomposition.md
docs/architecture/workflows/refinement-control-plane.md
the full affected workflow directory, especially:
- orchestrator.yaml
- transition_graph.yaml
- agents.yaml
- structured_outputs.yaml
- tools.yaml
- context_variables.yaml
- middleware.yaml
the relevant shared workflow surfaces when build lifecycle or shared tools change:
- factory_app/workflows/_shared/platform/build_lifecycle.py
- factory_app/workflows/_shared/ui/** for reusable workflow React components
- any affected factory_app/workflows/_shared/** helper
generated artifact contracts when AppGenerator or AgentGenerator is affected:
- factory_app/build_context/AppGenerator/file_contracts.yaml
- relevant workflow-converter or materialization contracts

Build input structure:

Build contexts are named directories with one context.yaml registry.
context.yaml declares explicit assets[]; folder names are organization, not policy.
Factory prompt catalogs are assets[] with kind: catalog under factory_app/build_context/{context_name}/.
Workflow runtime YAML (agents.yaml, context_variables.yaml, structured_outputs.yaml, middleware.yaml) stays under factory_app/workflows/{WorkflowName}/.
Hooks resolve factory build-context paths through factory_app.workflows._shared.hook_utils.workflow_context_path().
Do not recreate factory_app/workflows/_shared/catalogs/.
Do not add one-off catalog family folders such as patternbook/ for a single workflow unless there is a real organization need and the file is still declared in assets[].
Do not put large static prompt catalogs in context_variables.yaml; hooks inject them deterministically.
Reusable workflow React components belong under factory_app/workflows/_shared/ui/ when multiple factory workflows consume them.
Shared workflow UI is not auto-registered; each consuming workflow must import and re-export/register it from its own factory_app/workflows/{WorkflowName}/ui/index.js.
Do not import UI from a sibling workflow folder. Move shared UI into _shared/ui/, or keep a workflow-specific wrapper in the owning workflow's ui/ folder.
Reusable OSS build packs are named build contexts, not placeholder manifests. Add a pack only when context.yaml contains a pack: descriptor plus useful capabilities/facades and declares real assets[].
Pack instructions are assets[] with kind: contract.
Pack template directories are assets[] with kind: templates; they mirror generated app structure: templates/modules/..., templates/services/..., templates/ui/..., templates/config/.... YAML in template assets is generated app declarative output, not a build-context contracts lane.
Workspace build contexts use the same named-context shape under workspace-root build_context/{context_name}/.
the narrowest matching tests before editing:
- sequence, transition, and entrypoint routing: tests/test_pack_schema_models.py, tests/test_pack_config_paths.py, tests/test_existing_app_discovery_contracts.py
- build lifecycle hooks: tests/test_build_lifecycle_hooks.py
- ExistingAppDiscovery: tests/test_existing_app_discovery_contracts.py, tests/test_existing_app_discovery_native_migration.py
- AppGenerator: tests/test_appgenerator_canonical_generation.py, tests/test_appgenerator_module_contracts.py, tests/test_appgenerator_persistence_alignment.py
- AgentGenerator: tests/test_agentgenerator_workflow_converter.py, tests/test_agentgenerator_tool_planning.py, tests/test_agentgenerator_ui_quality_gate.py
- artifact routing and control-plane linkage: tests/test_control_plane_loader.py, tests/test_control_plane_tools.py, tests/test_hook_file_contract_context.py, tests/test_hook_domain_catalog_context.py, tests/test_build_lifecycle_hooks.py

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

10d ago First seen · 180 lines · 45 tokens per session scan A 9b603751f9ec

Subscribe to this mod's changes

factory-build-workflow-change is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 2,452 once invoked, about $0.0002 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.

Building agents LLM Planning agent-framework agentic-ai ai ai-agents genai

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

mozaiks: Skill for Claude Code