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 makifbaysal/tasktrooper --skill mobile-accessibilitygit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/mobile-accessibility)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/mobile-accessibility"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/mobile-accessibility/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/skills/makifbaysal/tasktrooper/mobile-accessibility"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/mobile-accessibility.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.00046 | $0.01272 |
| Opus 5.5 | $0.00018 | $0.00509 |
| Sonnet 5.5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
mobile-accessibility 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Accessibility
Overview
VoiceOver and TalkBack are not an edge case — they're how a meaningful share of your users, and every store review, go through the screen. Every control that is interactive needs a label a screen reader can speak; every screen needs a sane reading and focus order; text needs to scale.
Core principle: build it accessible the first time — retrofitting labels after the fact means re-testing the whole screen.
Per-stack API table
| Concern | Flutter | Compose | SwiftUI |
|---|---|---|---|
| Label | Semantics(label:) / tooltip / semanticLabel on Image/Icon |
contentDescription (null = decorative) |
accessibilityLabel / Button("…", systemImage:) |
| Grouping | MergeSemantics |
Modifier.semantics(mergeDescendants = true) |
.accessibilityElement(children: .combine) |
| Heading | Semantics(header: true) |
semantics { heading() } |
.accessibilityAddTraits(.isHeader) |
| Hidden/decorative | ExcludeSemantics |
Modifier.clearAndSetSemantics {} |
Image(decorative:) |
| Custom action | CustomSemanticsAction |
Modifier.semantics { customActions = … } |
.accessibilityAction(named:) |
| Live region | Semantics(liveRegion: true) |
Modifier.semantics { liveRegion = … } |
.accessibilityAddTraits(.updatesFrequently) |
Rules that apply everywhere:
- Every interactive control (button, icon button, tappable row) has a non-empty, human-readable label — never a bare icon with no text or label.
- Don't rely on a swipe-only gesture for something achievable another way; add a custom action or a visible control alongside it.
- Group a composite control (e.g. an icon + label that act as one tap target) with the merge/combine API so a screen reader announces it once, not as separate stops.
- Headings get the heading trait so screen-reader users can jump by section.
@ScaledMetric(SwiftUI) / theme text styles (Flutter, Compose) everywhere text appears — never a hardcoded point/sp size that ignores the system font-scale setting.- Respect reduce-motion:
MediaQuery.disableAnimationsOf(context)(Flutter),LocalAccessibilityManager/animation duration checks (Compose),@Environment(\.accessibilityReduceMotion)(SwiftUI) — skip or shorten a decorative animation, never a functional state change. - Contrast: body text ≥4.5:1, large text ≥3:1 against its background in both light and dark — check this when picking theme token values, not per-screen.
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.
- 8d ago First seen · 76 lines · 46 tokens per session scan A a1ea7cd5300f
mobile-accessibility is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 1,272 once invoked, about $0.0002 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-05.
Other skills, from other repositories
wireframe
Produce low-fidelity black-and-white UI wireframes as SVGs or viewer pages. Use when asked to wireframe, sketch a screen, draft a layout, make a low-fi mockup, or publish wireframes.
gamified-app
A multi-frame gamified mobile-app prototype — three phone frames on a dark showcase stage. Frame 1: cover / poster, Frame 2: today's quests with XP ribbons and a level bar, Frame 3: quest detail. Vivid quest tiles, level ribbon, bottom tab bar. Use when the brief asks for a "gamified app", "habit tracker", "RPG-style…
design-critique
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
wireframe-mobile-flow
A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames laid out in a row on a board, showing a connected user flow (Onboarding → Home feed → Item detail → Confirm). Grey-box content inside each device, dashed connector arrows + numbered step labels between screens, and a couple of annotation callouts.…
mobile-app
A mobile-app screen rendered inside a pixel-accurate iPhone 15 Pro frame on the page. Built by copying the seed assets/template.html and pasting one screen archetype from references/layouts.md. Use when the brief asks for "mobile app", "iOS app", "Android app", "phone screen", or "app UI".
mobile-onboarding
A three-screen mobile onboarding layout: an opening screen, a value explanation, and a sign-in or continue screen. It includes phone-style status details, progress dots, and a main button.