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.
curl -O https://raw.githubusercontent.com/BlocUnited-LLC/mozaiks/main/.agents/skills/appgenerator-change/SKILL.mdgit clone --depth 1 https://github.com/BlocUnited-LLC/mozaiksWrote 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/blocunited-llc/mozaiks/appgenerator-change)<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/appgenerator-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/appgenerator-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.
<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/appgenerator-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/appgenerator-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.01962 |
| Opus 5 | $0.00018 | $0.00981 |
| Sonnet 5 | $0.00007 | $0.00392 |
| Haiku 4.5 | $0.00004 | $0.00196 |
Grade A, and why
appgenerator-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 9d 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 — 167 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 AppGenerator specifically.
Typical triggers:
factory_app/workflows/AppGenerator/**- AppGenerator agents or prompts
AppBuildPlanshape or validationstructured_outputs.yamlfactory_app/build_context/AppGenerator/file_contracts.yamlfactory_app/build_context/AppGenerator/domain_catalogs.yamlfactory_app/build_context/AppGenerator/module_archetypes.yamltools/app_build_plan.pytools/assemble_app_tasks.py- shared generated UI contract checks used by AppGenerator
- module, page, or data contract generation behavior
- managed-capability or external-adapter planning
- app-owned facade module patterns
- AppGenerator-specific tests or fixtures
Inspect first:
factory_app/workflows/AppGenerator/agents.yamlfactory_app/workflows/AppGenerator/structured_outputs.yamlfactory_app/workflows/AppGenerator/middleware.yamlfactory_app/workflows/AppGenerator/transition_graph.yamlfactory_app/workflows/AppGenerator/context_variables.yamlfactory_app/build_context/AppGenerator/file_contracts.yamlfactory_app/build_context/AppGenerator/domain_catalogs.yamlfactory_app/build_context/AppGenerator/module_archetypes.yamlfactory_app/workflows/AppGenerator/tools/app_build_plan.pyfactory_app/workflows/AppGenerator/tools/assemble_app_tasks.pyfactory_app/workflows/_shared/generated_ui_contract.py
Catalog placement rule:
- AppGenerator prompt catalogs live only under
factory_app/build_context/AppGenerator/. - AppGenerator runtime workflow files live under
factory_app/workflows/AppGenerator/. - 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 static prompt catalog values to
context_variables.yaml; context variables are runtime/session state. - the narrowest relevant AppGenerator tests before editing:
tests/test_appgenerator_module_contracts.pytests/test_appgenerator_canonical_generation.pytests/test_appgenerator_persistence_alignment.pytests/test_appgenerator_validate_wiring.pytests/test_appgenerator_ui_quality_gate.pytests/test_appgenerator_component_drift_guard.pytests/test_appgenerator_managed_capability_smoke.pytests/test_appgenerator_generated_page_binding.py
- inspect upstream build-sequence context only when the AppGenerator change depends on upstream inputs or assumptions from
ValueEngine,ThemeCapture,DesignDocs, orAgentGenerator
Core truth:
- AppGenerator is the final app-bundle generation workflow inside the broader factory
workflow_sequence. - It consumes upstream outputs from earlier build workflows.
- It does not own product strategy, concept formation, brand discovery, or workflow generation.
- It emits canonical app workspace artifacts.
- It must respect the canonical app structure and the platform's current runtime contracts.
- It must respect
factory_app/build_context/AppGenerator/file_contracts.yaml. - It must not invent runtime contracts unsupported by the platform.
- It must not generate provider-owned managed capability internals.
- It should keep persistent app UI schema-first unless the bounded custom route contract is explicitly required.
Boundary rules:
- Do not treat AppGenerator as the whole build system.
- Do not change
workflow_sequencecomposition from this skill; usefactory-build-workflow-changewhen the change widens intoextension_registry.json, transitions, entrypoints, or cross-workflow build composition. - Do not generate
backend/models.pyorbackend/models/*.py. - Do not generate
contracts/subscriptions.yamlas the canonical reaction contract. - Do not generate flat root manifests when the canonical contract uses
contracts/. - Do not generate
app/capability_packs/. - Do not generate
transport.pyor duplicate runtime transport infrastructure. - Do not bind pages directly to managed-capability internals; use the app-owned facade module pattern.
- Do not hardcode provider-specific or private product examples into OSS guidance, tests, or fixtures.
- Do not assume
ctx.db; use the canonical persistence model andctx.persistence.collection(module_id, entity_name). - Do not generate local visual primitive clones or raw persistent-page React when the shipped schema and primitive contracts can represent the surface.
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.
- 9d ago First seen · 167 lines · 37 tokens per session scan A 4374d554de3a
appgenerator-change is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,962 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.
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…
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.
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 …
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…
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…
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.