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 commands/adobecom/da-express-milo/build-express-blockgit clone --depth 1 https://github.com/adobecom/da-express-miloWrote 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/commands/adobecom/da-express-milo/build-express-block)<a href="https://agentmods.dev/commands/adobecom/da-express-milo/build-express-block"><img src="https://agentmods.dev/badge/commands/adobecom/da-express-milo/build-express-block.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.00019 | $0.00895 |
| Opus 5 | $0.00010 | $0.00447 |
| Sonnet 5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
build-express-block 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-express-block
Orchestrates the build-content-from-figma and build-block-from-figma skills end-to-end: gather inputs once, author the content document, capture the resulting .aem.live URL, then build the Express block against that page.
Phase A — Gather all inputs upfront
Ask the user for the following in a single message. Collect every value before invoking either skill.
| Input | Required | Notes |
|---|---|---|
| Figma URL — Mobile (< 600 px) | At least one of the five | Frame link |
| Figma URL — Small Tablet (600–899 px) | Frame link | |
| Figma URL — Large Tablet (900–1199 px) | Frame link | |
| Figma URL — Desktop (≥ 1200 px) | Frame link | |
| Figma URL — Widescreen (≥ 1680 px) | Frame link (optional) | |
| DA organization | Yes | e.g. adobecom |
| DA repository | Yes | e.g. da-express-milo |
| DA file path | Yes | e.g. drafts/<ldap>/my-block |
| Block name override | No | Skip if you want the content skill to infer from Figma metadata |
| Base branch (block skill) | No | Default stage |
Validation:
- At least one Figma URL is mandatory.
- Org, repo, and DA path are all mandatory.
- Do not proceed until every required input is provided.
Show the collected inputs back to the user and ask for one confirmation before kicking off the chain.
Phase B — Run the content skill
Invoke the build-content-from-figma skill via the Skill tool. Hand it the Figma URLs (with their viewport labels), the DA org/repo/path, and the block name override if the user provided one.
The content skill has its own internal prompts (block name confirmation, diff review, upload confirmation, preview/publish confirmation). Let the user answer those directly — do not pre-answer or skip them.
When the content skill reaches Phase 7 (Preview & Publish), the user must opt in to publishing for the chain to continue. If they decline, stop here and tell the user the block skill needs an .aem.live URL to run.
Phase C — Capture the live URL
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.
- 5d ago First seen · 88 lines · 19 tokens per session scan A 6d15619d48d0
build-express-block is a command published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 895 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.