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.
git clone --depth 1 https://github.com/MoizIbnYousaf/marketing-cliWrote 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/moizibnyousaf/marketing-cli/update-chrome-binaries-test-region)<a href="https://agentmods.dev/commands/moizibnyousaf/marketing-cli/update-chrome-binaries-test-region"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/update-chrome-binaries-test-region/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/commands/moizibnyousaf/marketing-cli/update-chrome-binaries-test-region"><img src="https://agentmods.dev/badge/commands/moizibnyousaf/marketing-cli/update-chrome-binaries-test-region.svg" alt="Reviewed on agentmods" width="80" 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.01455 |
| Opus 5 | $0.00000 | $0.00727 |
| Sonnet 5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00145 |
Grade A, and why
update-chrome-binaries-test-region scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `packages/renderer/src/browser/get-chrome-download-url.ts`: `TESTED_VERSION` constant, `PLAYWRIGHT_VERSION` constant, and the trailing `// <version>` comment on the `PLAYWRIGHT_VERSION` line. Also update the two hard-c How it starts
The opening of the file, as written. The whole thing — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- Confirm the AWS CLI is logged into account
678892195805by runningaws sts get-caller-identity. If not, ask the user to log in. - Export AWS credentials into the shell by running
eval "$(aws configure export-credentials --format env)"(the lambda-client checks forAWS_ACCESS_KEY_IDand does not pick up SSO/Identity Center credentials on its own). - From
packages/lambda, runbun src/admin/make-layer-public.ts --region=eu-central-1to publish all 5 layers (fonts, chromium, emoji-apple, emoji-google, cjk) to a single test region. Flags supported by the script:--region=<region>publishes to a single region (use this for the test phase).--skip=<region1>,<region2>excludes regions when publishing to all (use this for the rollout phase, e.g.--skip=me-south-1to skip a region whose binaries are intentionally not being updated).- Omit both flags to publish to every region in
getRegions().
- The
evaland thebuncommand must run in the same shell invocation (chain with&&), since the env vars do not persist acrossBashtool calls. - Verify the output prints a
LayerArnandVersionfor each of the 5 layers and a final JSON dump with the published regions populated. - Update
packages/lambda/src/shared/hosted-layers.tsby copying the JSON dump from the script's stdout — do NOT manually bump version numbers. The script prints (after several blank lines) a completeHostedLayersobject showing the exactlayerArnandversionAWS returned for every layer it just published. Replace the corresponding region entries inhosted-layers.tswith those values. For the test phase (--region=eu-central-1), onlyeu-central-1is updated; other regions intentionally stay on their old versions until the rollout phase. - If you invoked the script with
--skip=<region>, leave those skipped regions untouched inhosted-layers.ts. - Update Chrome version references throughout the codebase. Ask the user for both the Chrome version (e.g.
149.0.7790.0) and the corresponding Playwright revision (look it up inhttps://github.com/microsoft/playwright/blob/main/packages/playwright-core/browsers.jsonif the user does not provide it — match bybrowserVersion). Files to update:packages/renderer/src/browser/get-chrome-download-url.ts:TESTED_VERSIONconstant,PLAYWRIGHT_VERSIONconstant, and the trailing// <version>comment on thePLAYWRIGHT_VERSIONline. Also update the two hard-codedhttps://remotion.media/chromium-headless-shell-amazon-linux-{arm64,x64}-<version>.zipURLs — but first verify the new binaries exist by runningcurl -sIagainst the new URLs (and the templatedchromium-headless-shell-linux-{arm64,x64}-<version>.zip?clearcacheURLs that followTESTED_VERSION). Only proceed when all return HTTP 200; otherwise ask the user to upload the missing builds toremotion.mediafirst.packages/lambda/src/admin/make-layer-public.ts: theChromium <version>, compiled from source.license string passed toPublishLayerVersionCommand.packages/docs/docs/lambda/runtime.mdx: prepend a new row to the "Chrome" version table for the next Remotion release. Determine the next version withcat packages/core/package.json | grep '"version"'and increment the patch.packages/docs/docs/miscellaneous/chrome-headless-shell.mdx: prepend a new row to the version table, and update the example version string in the "Version tracking" section.packages/docs/docs/renderer/ensure-browser.mdx: update bothversion: '<old>'occurrences in the example code blocks.
- Run the Docker matrix tests in
packages/dockerfiles/(./run.sh) against the new Chrome binary. Each Dockerfile renders two compositions from theBrowserTestRoot:browser-test(Three.js / WebGL / codec smoke test) andhtml-in-canvas(experimental WICGdrawElementImage()+canvas.requestPaint()APIs). Outputs land inpackages/dockerfiles/out/<platform>.mp4andpackages/dockerfiles/out/<platform>-html-in-canvas.mp4. Make sure Docker Desktop is running first. - The Dockerfiles install the local workspace build of
@remotion/cli+ transitive deps (not the published version), so source changes in@remotion/renderer(e.g. new Chrome flags) are picked up before publishing.run.shrunspack-cli.tswhich auto-walks@remotion/cli's transitiveworkspace:*deps, runsbun pm packfor each intopackages/dockerfiles/tarballs/, and emitslocal-cli-package.json(lists every tarball as a direct dep AND inoverrides, to force resolution to the local copies). Each Dockerfile thenCOPYstarballs/andlocal-cli-package.jsonand runsbun install+ addsnode_modules/.binto PATH. - If a new composition is added to the Docker test matrix, register it in
packages/example/src/BrowserTestRoot.tsx(so it is included in the bundle built fromsrc/browser-test-entry.ts) and add a correspondingRUN remotion render /usr/app/bundle <id> /usr/app/<filename>.mp4line +docker cpextraction inrun.sh. - The
html-in-canvascomposition's runtime check (packages/example/src/HtmlInCanvas/html-in-canvas.tsx) requires bothctx.drawElementImageandcanvas.requestPaint, which Chrome 149+ exposes when--enable-features=CanvasDrawElementis passed (already wired intofeaturesToEnable()atpackages/renderer/src/open-browser.ts:50). Ifhtml-in-canvasrenders fail with"HTML in Canvas is not supported"whilebrowser-testpasses, the most likely cause is a Chrome version mismatch — e.g. the Dockerfiles are using a published@remotion/cliwhoseTESTED_VERSIONpredates the new Chrome, so it re-downloads the older binary on top of the oneensure.mjsalready fetched. The local-tarball install path inpack-cli.ts+local-cli-package.jsonis what guaranteesensure.mjsand the render CLI agree on the sameTESTED_VERSION. - Do not proceed to publishing all regions until the test region has been verified end-to-end.
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.
- 6d ago First seen · 22 lines · 0 tokens per session scan A 64423d130f24
update-chrome-binaries-test-region is a command published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,455 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…
migration
Generate Prisma database migration.
cost-optimize
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with cost optimize in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.