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 cuesoftinc/oss-engineering-standards --skill cuelabs-mobile-standardgit clone --depth 1 https://github.com/cuesoftinc/oss-engineering-standardsWrote 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/cuesoftinc/oss-engineering-standards/cuelabs-mobile-standard)<a href="https://agentmods.dev/skills/cuesoftinc/oss-engineering-standards/cuelabs-mobile-standard"><img src="https://agentmods.dev/badge/skills/cuesoftinc/oss-engineering-standards/cuelabs-mobile-standard/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/cuesoftinc/oss-engineering-standards/cuelabs-mobile-standard"><img src="https://agentmods.dev/badge/skills/cuesoftinc/oss-engineering-standards/cuelabs-mobile-standard.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.00060 | $0.00489 |
| Opus 5 | $0.00030 | $0.00244 |
| Sonnet 5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
cuelabs-mobile-standard 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 10d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CueLABS Mobile Standard
Build mobile surfaces only after the product has approved mobile scope and design frames. Keep product behavior consistent across clients without forcing web chrome or interaction idioms onto mobile.
Required reference
Read references/flutter-implementation.md before changing a Flutter application, its native platform projects, mobile tests, mobile workflows, or mobile architecture.
Workflow
- Inspect
.cuelabs/project.yaml, mobile documentation, Figma frames, the Flutter tree, flavors, and current tests. - Confirm mobile is
active. If it isplanned, do not runflutter createor add mobile CI unless the user explicitly starts the mobile phase. - Map the work to feature-first presentation, domain, data, app, routing, or core layers.
- Preserve abstract repositories and environment-specific provider overrides. Keep remote APIs and fakes behind the same interfaces.
- Implement screens only when a corresponding approved frame and flow exist.
- Use shared design-system primitives for recurring interaction patterns.
- Update code generation outputs, tests, and documentation together.
- Run formatting, codegen-fresh checks, analysis, unit/widget tests, relevant goldens, and a platform build proportionate to the change.
- Clean regenerable build state at closeout.
Guardrails
- Do not create empty native or Flutter applications for future plans.
- Do not wire production APIs before the repository interfaces and product contracts are ready.
- Do not hand-edit generated code or generated token output.
- Do not silently delete quarantined legacy code.
- Do not generate golden baselines on an incompatible host and weaken tolerances to hide the difference.
- Do not use screen-local state invalidation when a domain mutation affects sibling surfaces.
- Do not ship a mobile screen without an approved design frame.
Result format
Report the product state, frames and contracts consulted, architectural layers changed, platform-specific decisions, tests/builds run, and remaining external dependencies.
What ships with it
2 files 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.
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.
- 10d ago First seen · 53 lines · 60 tokens per session scan A a454b864030b
cuelabs-mobile-standard is a skill published in the GitHub repository cuesoftinc/oss-engineering-standards (2 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 489 once invoked, about $0.0003 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-31.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
dev-workflow
The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.
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.
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…