A deployment skill for AWS Lambda, a service that runs code without managing servers. It packages the code for the wi-router and pr-router automation agents and uploads it to Lambda.

Use it to deploy either router or both routers after code changes, using names from .ai/automation/infra.json.

It removes the manual work of building deployment packages and finding the correct Lambda functions and region.

auto-deploy — Skill for Claude Code and Codex by easingthemes: A deployment skill for AWS Lambda, a service that…

Install

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.

agentmods

npx agentmods add skills/easingthemes/dx-aem-flow/auto-deploy

Any agent

npx skills add easingthemes/dx-aem-flow --skill auto-deploy

Clone the repo

git clone --depth 1 https://github.com/easingthemes/dx-aem-flow

Made for: Claude Code, Codex.

Or install dx-automation, the plugin that ships this one along with the rest of its 11 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/auto-deploy.svg)](https://agentmods.dev/skills/easingthemes/dx-aem-flow/auto-deploy)

Your own site

<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/auto-deploy"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/auto-deploy.svg" alt="Measured on agentmods" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,474 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00054	$0.01474
Opus 5	$0.00027	$0.00737
Sonnet 5	$0.00011	$0.00295
Haiku 4.5	$0.00005	$0.00147

Measured 4d ago against content hash d05620c4368f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auto-deploy 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 4d 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.

plugins/dx-automation/skills/auto-deploy/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You deploy Lambda function code for the 2 AI automation agents (wi-router, pr-router). Wraps lambda/deploy.sh with audit logging. Safe to re-run at any time after code changes.

0. Prerequisites

Read .ai/automation/infra.json. Check automationProfile:

If consumer (or legacy pr-only/pr-delegation): "This repo uses the consumer profile — Lambda functions are managed by the hub project. Do NOT deploy Lambda from this repo." STOP.

source .ai/lib/audit.sh
export AUDIT_LOG_PREFIX=infra

Extract Lambda function names and region from infra.json.

Verify: zip is installed (which zip). If missing: "Install zip: brew install zip (macOS) or apt install zip (Linux)". STOP.

1. Parse Target

Default target: all. If user passed an argument (wi-router, pr-router), use that.

2. Deploy

cd .ai/automation
bash lambda/deploy.sh <target>

The deploy script reads function names and files from infra.json, packages each Lambda + shared libs into a zip, and calls aws_lambda_deploy (audit-wrapped).

Report output from the script.

What ships with the Lambda

The Lambda zip contains only the webhook router code (wi-router.mjs / pr-router.mjs) and shared libs (dedupe.js, dlq.js, rate-limiter.js, aws-sig.js, retry.js). The Lambda's job is to route webhook events to ADO pipelines — it does not run agents.

Agent code, MCP config, and pipeline YAML are not in the Lambda zip. They live in the dx-aem-flow plugin repo and are pulled by each pipeline at runtime:

Asset	Location	Distributed via
Agent skills (`/dx-simple`, `/dx-pr-review`, …)	`plugins/dx-*/skills/`	Marketplace clone in pipeline YAML (`git clone dx-aem-flow.git`)
Pipeline YAML (`ado-cli-simple.yml`, …)	`plugins/dx-automation/data/pipelines/cli/`	Imported into ADO once via `/auto-pipelines`
Pipeline MCP overrides (`simple-mcp.json`, …)	`plugins/dx-automation/data/mcp/`	Marketplace clone — pipeline copies into `.mcp.json` at runtime

Read the full file on GitHub · 120 lines

Changes

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.

4d ago First seen · 120 lines · 54 tokens per session scan A d05620c4368f

Subscribe to this mod's changes

auto-deploy is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,474 once invoked, about $0.0003 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-31.

DevOps and cloud Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens