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.
/plugin marketplace add adobe/skillsnpx agentmods add plugins/adobe/skills/edge-delivery-services-content-opsgit clone --depth 1 https://github.com/adobe/skillsGrade A, and why
aem-eds-content-ops 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 3d 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.
What it actually says
{
"name": "aem-eds-content-ops",
"description": "Content operations skills for AEM Edge Delivery Services: page auditing, SEO optimization, AI search (GEO), WCAG accessibility, bulk metadata, structured data, sitemap validation, and content diffing. Complements the EDS development skills with operational tooling for content teams.",
"version": "1.0.0",
"author": {
"name": "FocusGTS"
},
"repository": "https://github.com/adobe/skills",
"license": "Apache-2.0",
"keywords": ["aem", "edge-delivery-services", "content-ops", "seo", "geo", "accessibility", "wcag", "metadata", "audit"]
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 373 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 12 lines scan A 88fef3d63a91
aem-eds-content-ops is a plugin published in the GitHub repository adobe/skills (175 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.
aomi
Aomi for AI agents — drive the Aomi CLI from natural-language prompts (chat, simulate, sign on-chain transactions with account-abstraction-aware execution) and scaffold new Aomi apps from API specs. Bundle ships two skills: aomi-transact (run on-chain across 40+ DeFi/perps/CEX/social apps on EVM mainnets and L2s) and…
skillctx
Make your agent skills portable by extracting hardcoded values into a central config and embedding resolver scripts.
auth
Auth skills for Claude Code — scaffold hand-rolled auth endpoints and audit auth code against security best practices.
decision-making
Master architectural decision-making: ADRs, technology selection, build-vs-buy analysis, proof of concepts, and migration planning.
enterprise-team
Complete virtual company with 76 specialized AI agents across Engineering, Product, Infrastructure, Data, Security, Marketing, Sales, Finance, Legal, and People. Pipeline modes (Full/Sprint/Micro), Dev↔QA loops, quality gates, and handoff protocols.