Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/divinevideo/divine-mobilenpx agentmods add skills/divinevideo/divine-mobile/e2e-testWrote 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/divinevideo/divine-mobile/e2e-test)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/e2e-test"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/e2e-test/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/divinevideo/divine-mobile/e2e-test"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/e2e-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 135 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00048 | $0.03747 |
| Opus 5.5 | $0.00019 | $0.01499 |
| Sonnet 5.5 | $0.00010 | $0.00749 |
| Haiku 4.5 | $0.00005 | $0.00375 |
Grade B, and why
e2e-test scanned grade B with 1 finding 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 20d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
find it: sudo lsof -nP -iTCP:45173 -sTCP:LISTEN How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Integration Testing
Goal: run the real app against a real local backend, end-to-end.
OAuth, relay subscriptions, and media uploads all hit local Docker
services — no mocks anywhere. Tests live in
mobile/integration_test/, backend in local_stack/.
Run a test
Two terminals, from mobile/:
# Terminal 1 — emulator
mise run emulator
# Terminal 2 — tests
mise run e2e_test # All auth tests
mise run e2e_test integration_test/auth/auth_journey_test.dart # Single test
e2e_test brings up the Docker stack, runs the suite, captures a
merged docker+logcat+app timeline at test_reports/*.jsonl, and
prints the native test XML path + failure excerpts when the APK
fails to install. For e2e targets, never call patrol test or
flutter test directly — you'll lose the timeline and the diagnostics.
Not every suite is a patrol suite. profile.sh recursively greps the
target for patrolTest and dispatches: patrol suites go to
patrol test, plain integration_test suites go to
flutter test --device-id. Everything under integration_test/e2e/
is now the plain kind. The original four converted off patrol in #7005 because
none used the native automator for anything load-bearing, and new suites should
follow that pattern. The plain path pre-grants POST_NOTIFICATIONS, since
without an automator nothing can dismiss that dialog.
Version pair
patrol (the package) and patrol_cli (the binary) ship as a matched
pair, and patrol_cli enforces it at run time — a mismatch aborts the
run before any test executes.
| Half | Version | Declared in |
|---|---|---|
patrol package |
4.9.0 | mobile/pubspec.yaml (patrol: ">=4.9.0 <4.10.0") |
patrol_cli binary |
4.7.0 | local_stack/profile.sh (PATROL_CLI_VERSION) |
profile.sh checks the installed CLI and runs
dart pub global activate patrol_cli <version> when it differs, so
mise run e2e_test self-heals. That activation is machine-global:
it switches the CLI for every checkout, including worktrees still on an
older patrol, which will then fail the same compatibility check until
they rebase. Change the two versions together — the compatibility table
is at https://patrol.leancode.co/documentation/compatibility-table.
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.
- 20d ago Changed · +9 lines 2c1d08fe2b41
- 21d ago Changed · +25 lines 94225b0ea8b8
- 23d ago Changed · +13 lines 0ce4e69601c1
- 1mo ago Changed · -47 lines 0d338a76d888
- 1mo ago Changed ed8c6f9b1176
- 1mo ago Changed · +9 lines 47dd01fb302d
- 1mo ago First seen · 381 lines · 48 tokens per session scan B 9ec6ef4055d3
e2e-test is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 48 tokens to every session and 3,747 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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.…
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…
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.
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.
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.