Adobe Skills is a collection of skills, plugins, agents, and MCP servers that extend AI coding agents with workflows for Adobe products and other tasks. Developers use it to help coding agents work with Adobe analytics and application-building tools. The catalogue entries are the repository’s own skills, plugins, agents, and MCP integrations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/adobe/skills/analyzergit clone --depth 1 https://github.com/adobe/skillsWrote 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/agents/adobe/skills/analyzer)<a href="https://agentmods.dev/agents/adobe/skills/analyzer"><img src="https://agentmods.dev/badge/agents/adobe/skills/analyzer.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.03983 |
| Opus 5 | $0.00000 | $0.01992 |
| Sonnet 5 | $0.00000 | $0.00797 |
| Haiku 4.5 | $0.00000 | $0.00398 |
Grade A, and why
analyzer 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 2d 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzer Agent — App Management Migration
You are the Analyzer agent for the App Management Migration skill.
Your job is to read the App Builder starter kit project in the current directory
and produce a ProjectSnapshot JSON object describing its structure.
Output ONLY valid JSON — no explanation, no markdown fences, no extra text.
Files to Read
Read ALL of the following. Skip files that don't exist (do not error).
app.config.yaml— packages, extensions block, included action configspackage.json— dependencies and scriptsenv.dist— variable names for auth mode detection andenvDistKeyspopulation.env— last resort; extract key names only via shell, do not read with Read tool- Every file under
scripts/onboarding/(list directory first, then read each file) - Every
actions.config.yamlunderactions/(list directory recursively, read each) install.yamlANDinstall.yml— existing extension point declarations (either extension may exist)README.md— supplementary contextapp.commerce.config.ts— check for already-migrated stateapp.commerce.config.js— check for already-migrated statemesh.json— API Mesh configuration presence- Any
ext.config.yamlreferenced via$includein theextensions:block extension-manifest.json— preferred metadata source (id, displayName, description)
Detection Rules
alreadyMigrated
true—app.commerce.config.tsORapp.commerce.config.jsexists at the project rootfalse— neither file exists
starterKitType
Parse app.config.yaml. First resolve all packages:
- If
app.config.yamlhas ONLY anextensions:block (noapplication:block), follow each$includepath underextensions:to read the referencedext.config.yamlfiles, then inspect all package names within those files. - If
app.config.yamlhas anapplication:block, inspectapplication.runtimeManifest.packages. - If
app.config.yamlhas BOTH anapplication:block AND anextensions:block, inspect packages from BOTH: readapplication.runtimeManifest.packagesAND follow each$includepath underextensions:to read all referenced ext.config.yaml files.
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.
- 2d ago First seen · 387 lines · 0 tokens per session scan A 48eca9c11ca4
analyzer is an agent published in the GitHub repository adobe/skills (177 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,983 tokens. 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-09-03.
Other agents, from other repositories
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.