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 skills add skydoves/android-testing-skills --skill asserting-bounds-and-dimensionsgit clone --depth 1 https://github.com/skydoves/android-testing-skillsWrote 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/skills/skydoves/android-testing-skills/asserting-bounds-and-dimensions)<a href="https://agentmods.dev/skills/skydoves/android-testing-skills/asserting-bounds-and-dimensions"><img src="https://agentmods.dev/badge/skills/skydoves/android-testing-skills/asserting-bounds-and-dimensions.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.00255 | $0.03430 |
| Opus 5 | $0.00128 | $0.01715 |
| Sonnet 5 | $0.00051 | $0.00686 |
| Haiku 4.5 | $0.00026 | $0.00343 |
Grade A, and why
asserting-bounds-and-dimensions 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 7d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asserting Bounds and Dimensions — Layout Math in Dp, Not Pixels
Layout assertions belong in dp, run with a half-dp tolerance, and most of the interesting checks (padding, gap, alignment) are subtractions between two getUnclippedBoundsInRoot() rectangles. This skill picks the right size/position assertion, explains clipped vs unclipped, and shows the canonical "compute padding from two rects" pattern lifted directly from material3/ButtonTest.kt.
When to use this skill
- The developer wants to verify a Button is 48 dp tall, a Spacer is 16 dp wide, an Icon is at position
(24.dp, 12.dp). - The developer asks how to assert the padding between two composables.
- The developer asks about minimum touch target sizes (
ChipDefaults.MinHeight + 1.dp). - The developer is comparing layout values in pixels and wants the dp-typed equivalent.
- The developer mentions
assertWidthIsEqualTo,getUnclippedBoundsInRoot,DpRect,getAlignmentLinePosition,getFirstLinkBounds.
When NOT to use this skill
- The check is about state (enabled, on, selected) — see
./asserting-node-state-and-text/SKILL.md. - The check is "is the node on screen at all" —
assertIsDisplayed()is enough; bounds math adds friction without value. - The composable's bounds depend on an animation in flight — pause the clock first; see
../../synchronization/testing-animations-deterministically/SKILL.md. - The bounds are relative to a screenshot — use a screenshot test instead.
Prerequisites
- A working
ComposeTestRule/ComposeUiTest. See../../setup/configuring-test-dependencies/SKILL.md. - The target composable has finished measuring and placing. If it animates in, advance the test clock first — see
../../synchronization/controlling-the-test-clock/SKILL.md. - For touch-target assertions, the target node has a click action so
touchBoundsInRootis meaningful.
Workflow
- 1. Pick the assertion by question type. All APIs live in
commonMain/.../BoundsAssertions.kt.
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.
- 7d ago First seen · 216 lines · 255 tokens per session scan A 795430d3327f
asserting-bounds-and-dimensions is a skill published in the GitHub repository skydoves/android-testing-skills (318 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 255 tokens to every session and 3,430 once invoked, about $0.0013 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.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
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.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…