migrate-container-queries

A guide to replacing viewport media queries with container queries in Sentry’s frontend. Media queries respond to the browser window, while container queries respond to the space available around a component.

In plain words
What is it for?
Use it when converting @media rules, useMedia hooks, or screen-prefixed responsive properties to container-based layouts using Container, Flex, or Grid.
Why use it?
It helps responsive components fit their actual layout container, which is useful when the same component appears in differently sized areas.

Skill for Claude CodeCodex

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/getsentry/sentry/migrate-container-queries
Any agent
npx skills add getsentry/sentry --skill migrate-container-queries
Clone the repo
git clone --depth 1 https://github.com/getsentry/sentry

Made for: Claude Code, Codex.

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00076 $0.02299
Opus 5 $0.00038 $0.01149
Sonnet 5 $0.00015 $0.00460
Haiku 4.5 $0.00008 $0.00230

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

Security

Grade A, and why

migrate-container-queries 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.

.agents/skills/migrate-container-queries/SKILL.md · 137 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 2d ago First seen · 137 lines · 76 tokens per session scan A baac301d75b4

Subscribe to this mod's changes

migrate-container-queries is a skill published in the GitHub repository getsentry/sentry (44,660 stars, last pushed 2d ago), with no licence file. It adds 76 tokens to every session and 2,299 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

project-writing-collectors

Best practices and orientation for AI assistants authoring or modifying Netdata data-collection plugins or modules in any language. Read before adding a new collector, modifying an existing one, working on logs, topology, NetFlow/sFlow/IPFIX, OTEL ingestion, SNMP profiles, statsd, Prometheus scraping, or interactive…

netdata/netdata · 147 tokens

verify-worldmonitor

Launch and drive the WorldMonitor browser dashboard (Vite app at /dashboard) to prove user-facing behavior with screenshots and transcripts. Use when a change needs proof in the real app rather than only unit tests — panels, map layers, settings, search, country briefs, boot — or when asked to run, screenshot, or…

koala73/worldmonitor · 73 tokens

blogwatcher

Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.

mateaix/mateclaw · 18 tokens

playwright-cli

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

pgEdge/ai-dba-workbench · 52 tokens

Alerting & Monitoring Testing

Testing monitoring and alerting configurations including threshold validation, alert routing, escalation policies, and false-positive rate monitoring.

PramodDutta/qaskills · 28 tokens

prometheus

Prometheus monitoring — scrape configuration, service discovery, recording rules, alert rules, and production deployment for infrastructure and application metrics.

wpank/ai · 28 tokens