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/agentgenerator-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/agentgenerator-change)<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/agentgenerator-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/agentgenerator-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/agentgenerator-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/agentgenerator-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.00033 | $0.01568 |
| Opus 5 | $0.00016 | $0.00784 |
| Sonnet 5 | $0.00007 | $0.00314 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
agentgenerator-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 — 143 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 AgentGenerator specifically.
Typical triggers:
factory_app/workflows/AgentGenerator/**- AgentGenerator workflow prompts
- agent or workflow bundle structured outputs
- generated workflow scaffolds
- generated agent prompts
- generated
transition_graph.yaml,tools.yaml,structured_outputs.yaml, orcontext_variables.yaml - universal prompt injection
- MCP or tool capability injection
- workflow or agent safety rules
- agent-generated runtime behavior guidance
- AgentGenerator tests or fixtures
Inspect first:
factory_app/workflows/AgentGenerator/agents.yamlfactory_app/workflows/AgentGenerator/structured_outputs.yamlfactory_app/workflows/AgentGenerator/middleware.yamlfactory_app/workflows/AgentGenerator/transition_graph.yamlfactory_app/workflows/AgentGenerator/tools.yamlfactory_app/workflows/AgentGenerator/context_variables.yamlfactory_app/workflows/AgentGenerator/tools/hook_universal_prompts.py- capability-hook files if they exist in this workflow later, such as
hook_mcp_capabilities.pyoragent_capabilities.py factory_app/workflows/AgentGenerator/tools/tool_planning.pyfactory_app/workflows/AgentGenerator/tools/workflow_converter.pyfactory_app/workflows/AgentGenerator/tools/generate_and_download.pydocs/architecture/workflows/workflow-authoring-contracts.mddocs/architecture/builder/agentgenerator-output-assembly-contract.mddocs/architecture/workflows/workflow-routing-transitions.md- the narrowest matching AgentGenerator tests before editing:
tests/test_agentgenerator_workflow_converter.pytests/test_agentgenerator_tool_planning.pytests/test_agentgenerator_ui_quality_gate.pytests/test_agentgenerator_generate_and_download_collection.pytests/test_agentgenerator_generate_and_download_persistence.py
Core truth:
- AgentGenerator is one workflow inside the broader factory build
workflow_sequence. - It generates workflow and agent bundles, not app modules or persistent app pages.
- AppGenerator generates app bundle artifacts; AgentGenerator generates AI workflow artifacts.
- It should not own runtime substrate behavior.
- It should not own app page or module generation.
- It should not inject hosted or private product assumptions into generated agents.
- It should produce workflows that respect the current workflow authoring contracts.
- Generated workflow tools, hooks, and helpers stay workflow-local unless the current shared factory infrastructure explicitly owns the shared helper.
Boundary rules:
- Do not treat AgentGenerator as the whole build system.
- Do not change
workflow_sequencecomposition from this skill; usefactory-build-workflow-changewhen the change widens intoextension_registry.json, sequence design, transitions, entrypoints, or cross-workflow ownership. - Do not generate app modules or persistent app pages; that belongs to AppGenerator.
- Do not generate runtime transport, platform, or substrate code.
- Do not inject private hosted-product names, assumptions, or proprietary examples into prompts, scaffolds, tests, or docs.
- Do not use stale workflow fields like
startup_modewhen the current contract usesworkflow_startup_mode. - Do not create fake MCP or tool declarations unsupported by runtime or current workflow contracts.
- Do not bypass workflow-local handoff semantics.
- Do not use
workflow_sequenceas a HITL substitute.
Common change types:
- Prompt changes:
- inspect
agents.yaml,hook_universal_prompts.py, and the nearest prompt-hygiene tests together - preserve universal compliance and lane-discipline guidance
- inspect
- Structured output changes:
- inspect
structured_outputs.yamlplus the workflow authoring contract docs and converter tests - keep field names and enums aligned with current loader expectations
- inspect
- Universal prompt hook changes:
- inspect
hook_universal_prompts.py,middleware.yaml, and tests that validate prompt or UI-safety guidance - keep universal behavior separate from file-generation or pattern-specific hooks
- inspect
- MCP or tool capability hook changes:
- inspect
tool_planning.py,tools.yaml, and any capability hook files if present - add only runtime-supported tool declarations and workflow UI requirements
- inspect
- Workflow scaffold or file contract changes:
- inspect
workflow_converter.py,generate_and_download.py, and workflow authoring contract docs together - keep generated bundle files workflow-local and contract-bound
- inspect
- Handoff generation changes:
- inspect
transition_graph.yaml, converter tests, and authoring docs together - preserve workflow-local handoff semantics and exact cross-reference names
- inspect
- Tool generation changes:
- inspect
tools.yaml,tool_planning.py, and workflow UI contract tests together - keep tool declarations aligned with supported UI and lifecycle surfaces
- inspect
- Workflow safety or human-review guidance:
- inspect prompt injections, workflow authoring docs, and quality-gate tests together
- keep HITL semantics explicit inside the workflow bundle, not in
workflow_sequence
- Agent role or persona generation:
- inspect
agents.yaml,structured_outputs.yaml, and downstream scaffold expectations together - keep generated agents scoped to workflow behavior, not runtime ownership
- inspect
- Test or fixture updates:
- update the narrowest workflow-bundle fixture that changed
- keep examples provider-neutral and OSS-safe
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 · 143 lines · 33 tokens per session scan A 4c767c6606e1
agentgenerator-change is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,568 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.