boxel: Skill for Claude Code

.claude/skills/motion-testing/SKILL.md

motion-testing is a skill for Claude Code from cardstack/boxel. It costs 107 tokens per session (1,196 once invoked), scanned A, original, MIT.

A guide to testing animated interfaces with helpers that wait for motion to settle and inspect element geometry. It also covers test setup for the motion and Choreo libraries.

In plain words
What is it for?
Use it when testing animated elements, entering and leaving content, layout changes, Choreo regions, or elements that move to new positions.
Why use it?
It avoids unreliable tests that sleep for an assumed number of milliseconds. Tests instead wait for the animation system to finish and can detect leftover layout state or animation problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is cardstack/boxel's own configuration. It tells Claude Code how to work on boxel itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything boxel configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cardstack/boxel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/cardstack/boxel/main/.claude/skills/motion-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/cardstack/boxel

Made for: Claude Code.

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.

agentmods badge for motion-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/cardstack/boxel/motion-testing/github.svg)](https://agentmods.dev/skills/cardstack/boxel/motion-testing)
Your own site
<a href="https://agentmods.dev/skills/cardstack/boxel/motion-testing"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/motion-testing/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.

agentmods 80×15 button for motion-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/cardstack/boxel/motion-testing"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/motion-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,196 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00107 $0.01196
Opus 5.5 $0.00043 $0.00478
Sonnet 5.5 $0.00021 $0.00239
Haiku 4.5 $0.00011 $0.00120

Measured 5d ago against content hash ca085c1bab02, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

motion-testing 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.

.claude/skills/motion-testing/SKILL.md · 100 lines

How it starts

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

Testing motion

Never sleep(200). A sleep encodes a duration the test doesn't own; change a spring and every sleep becomes flaky or slow.

import { setupChoreo } from '@cardstack/choreo/test-support';
import {
  animationsSettled,
  bounds,
  shape,
} from 'glimmer-motion/test-support';

module('the inbox', function (hooks) {
  setupRenderingTest(hooks);
  setupChoreo(hooks);

  test('a deleted row flies to the bin', async function (assert) {
    await render(<template><Inbox /></template>);
    await animationsSettled();

    await click('[data-test-delete="row-2"]');
    await animationsSettled();

    assert.dom('[data-test-row="row-2"]').doesNotExist();
  });
});
  • setupMotion(hooks) — resets what outlives an owner: the projection root, the layout-loop guard, motion speed, and any reset registered with registerMotionReset(fn). Its afterEach also fails a test in which a layout loop ran. Always pair with setupRenderingTest.
  • setupChoreo(hooks) (@cardstack/choreo/test-support) — the setup for a suite that renders <Choreo>, in place of setupMotion. It is setupMotion plus Choreo's own resets: the beacon registry, the far-match barrier, gesture samples.
  • animationsSettled() — resolves when every motion element, layout animation and <Choreo> timeline in the document has stopped. On timeout it names what was still moving ({ timeout }, default 5000 ms; whatIsBusy() / isMotionIdle() are the probes it polls). It is deliberately NOT folded into settled(): a blocking waiter would turn "click again while it is still moving" into "wait for it to finish", and interruption tests would go green by no longer testing anything.
  • bounds(el) — measures relative to #ember-testing, not the viewport (QUnit moves and scales its container; raw getBoundingClientRect() answers a different question depending on how many tests have run).
  • shape(el) — the cumulative 2×2 transform. The way to assert a label was not smeared by its parent's scale; reading x will never tell you.
  • orphanCount() / strandedTransforms() (@cardstack/choreo/test-support) — the two invariants to assert after any interruption test: nothing parked in a Choreo orphan layer, nothing wearing a transform nobody is animating.
  • live(selector) / liveAll(selector) (@cardstack/choreo/test-support) — query while a crossing may be aloft. A leaver's skin is parked in [data-choreo-orphans], so a bare querySelector can return the ghost rather than the live element.
  • advanceGate() opens every parked c.Gate and settles; seekTo(seconds) pauses every live run and sets its clock — the way to assert a frame mid-timeline without timing it.
  • Also in glimmer-motion/test-support: boundsAndShape(el) (both in one object) and velocityOf(el) (px/s, sampled across two frames).

Read the full file on GitHub · 100 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.

  1. 5d ago First seen · 100 lines · 107 tokens per session scan A ca085c1bab02

Subscribe to this mod's changes

motion-testing is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 1,196 once invoked, about $0.0004 per session on Opus 5.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-10-21.

Related

Other skills, from other repositories

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens