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/existing-app-discovery-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/existing-app-discovery-change)<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/existing-app-discovery-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/existing-app-discovery-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/existing-app-discovery-change"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/existing-app-discovery-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.00039 | $0.01725 |
| Opus 5 | $0.00019 | $0.00863 |
| Sonnet 5 | $0.00008 | $0.00345 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
existing-app-discovery-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 11d 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 — 145 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 brownfield or existing-app discovery flow.
Typical triggers:
factory_app/workflows/ExistingAppDiscovery/**brownfield_app_adoptioninfactory_app/workflows/extended_orchestration/extension_registry.json- existing app preload or discovery tools
- adoption levels or adoption rationale
embed,bridge,ecosystem, orgradual_modernizationdecisions- module decomposition outputs for brownfield adoption
- storage, connector, auth, or security detection
- brownfield artifact saving or downstream discovery artifact consumption
- ExistingAppDiscovery workflow-local handoffs or brownfield routing into later factory workflow contracts
Inspect first:
factory_app/workflows/extended_orchestration/extension_registry.jsondocs/architecture/workflows/workflow-routing-transitions.mddocs/architecture/orchestration-and-decomposition.mdfactory_app/workflows/ExistingAppDiscovery/agents.yamlfactory_app/workflows/ExistingAppDiscovery/structured_outputs.yamlfactory_app/workflows/ExistingAppDiscovery/transition_graph.yamlfactory_app/workflows/ExistingAppDiscovery/context_variables.yamlfactory_app/workflows/ExistingAppDiscovery/tools/preload_discovery_context.pyfactory_app/workflows/ExistingAppDiscovery/tools/save_existing_app_artifacts.pytests/test_existing_app_discovery_contracts.py- the narrowest matching brownfield routing tests before editing:
tests/test_existing_app_discovery_gradual_modernization.pytests/test_session_router.pytests/test_session_launcher.pytests/test_pack_schema_models.py
Core truth:
ExistingAppDiscoverybelongs to the brownfield or existing-app adoption flow.- It is not the default greenfield build path.
- It is not
AppGenerator. - It should analyze an existing app and produce structured adoption, discovery, and decomposition artifacts.
- It must not copy existing-app code directly into generated apps without a conscious adoption strategy.
- Separate docs and stated intent from code truth when evaluating an external app.
- Code truth wins over docs, screenshots, or product summaries when they conflict.
embed,bridge,ecosystem, andgradual_modernizationare current workflow-local adoption labels. They are discovery evidence, not canonical AppContext artifact kinds.brownfield_app_adoptioncurrently routes intoExistingAppDiscovery; it does not continue through the default greenfield build sequence unless the authored sequence contract changes.- Downstream factory workflow consumption should happen through saved artifacts and explicit contracts, not by pretending discovery is already
AppGenerator.
AppContext target direction:
ExistingAppDiscovery currently emits workflow-local outputs including ExistingProductSpec,
CapabilitySpec[], AgentAugmentationPlan, and optionally module_decomposition_plan. These are
retired evidence outputs — they are not canonical AppContextVersion artifact kinds and must not
become control-plane source of truth. The target canonical substrate for both greenfield and
brownfield apps is AppContextVersion. See
docs/architecture/foundations/app-context-and-brownfield-adoption.md.
Boundary rules:
- Do not make
ExistingAppDiscoverythe greenfield build path. - Do not make
AppGeneratorresponsible for brownfield discovery, preload scanning, or adoption classification. - Do not treat docs as the source of truth when analyzing an external app.
- Code truth wins.
- Do not copy provider-specific or proprietary implementation into OSS fixtures, examples, or tests.
- Use neutral fixture apps in tests.
- Do not copy existing-app code directly into generated apps as an implicit migration strategy.
- When old in-flight outputs use
native_migrationadoption level, treat that as retired historical discovery evidence feeding theAdoptionPlan/AppContextVersioncontracts — not as a canonical artifact kind to preserve or extend. - Keep
workflow_sequence, transition routing, and workflow-localtransition_graph.yamldistinct. - Do not assume later factory workflows are part of the brownfield path unless
extension_registry.jsonand the saved artifact contracts explicitly say so.
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.
- 11d ago First seen · 145 lines · 39 tokens per session scan A 601b2972019c
existing-app-discovery-change is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,725 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
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…
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-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.