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 TalissonVitorino/kmp-ios-skills --skill android-device-integritygit clone --depth 1 https://github.com/TalissonVitorino/kmp-ios-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/talissonvitorino/kmp-ios-skills/android-device-integrity)<a href="https://agentmods.dev/skills/talissonvitorino/kmp-ios-skills/android-device-integrity"><img src="https://agentmods.dev/badge/skills/talissonvitorino/kmp-ios-skills/android-device-integrity/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/talissonvitorino/kmp-ios-skills/android-device-integrity"><img src="https://agentmods.dev/badge/skills/talissonvitorino/kmp-ios-skills/android-device-integrity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Privilege Escalation · line 233 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00260 | $0.05295 |
| Opus 5.5 | $0.00104 | $0.02118 |
| Sonnet 5.5 | $0.00052 | $0.01059 |
| Haiku 4.5 | $0.00026 | $0.00530 |
Grade A, and why
android-device-integrity 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 1mo 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Device Integrity & Anti-Fraud
Prove a request comes from a genuine, unmodified build of your app, installed by Google Play, running on a real non-tampered Android device — not an emulator, a repackaged clone, a bot farm, or an instrumented (Frida/Xposed) copy. The hardware-backed root of trust is the Play Integrity API; everything else on this page is defense-in-depth around it.
-
SafetyNet Attestation is dead.
SafetyNetApi.attestwas deprecated and the service is fully shut down. Do not call it or copy old SafetyNet code — Play Integrity is the replacement. -
Not authentication. Integrity answers "is this a legitimate app instance on a genuine device?", not "who is the user?". Combine with real sign-in (
authentication) and a backend risk engine. -
The verdict is made on your server, never on the client. A rooted device can patch any local check to return "clean". Trust only a token your backend decrypted and verified.
-
iOS counterpart:
device-integrity(App Attest / DeviceCheck). -
Android primitives: Keystore,
EncryptedFile, network-security config, TLS pinning →mobile-security. -
KMP boundary: expose a
commonMaininterface DeviceIntegrityreturning an opaque token string; bind anandroidMainactualthat calls Play Integrity. Keep raw tokens out of shared code — pass the base64 through to your backend. Seeexpect-actual.
Contents
- Standard vs Classic — choosing
- Prerequisites
- Standard request — client flow
- Classic request — client flow
- The integrity verdict
- Server-side decryption & verification
- Root / emulator / hook detection (defense-in-depth)
- Fintech anti-fraud design
- Error handling
- Correctness checklist
- Reference:
references/server-verification.md
Standard vs Classic — choosing
Two request shapes on the same API. Prefer Standard for almost everything.
What ships with it
1 file 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.
- 1mo ago First seen · 357 lines · 260 tokens per session scan A f3d707e38bb5
android-device-integrity is a skill published in the GitHub repository TalissonVitorino/kmp-ios-skills (15 stars, last pushed 2mo ago), licensed MIT. It adds 260 tokens to every session and 5,295 once invoked, about $0.0010 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-08-30.
Other skills, from other repositories
compose-multiplatform
Use when building one shared Compose UI in Kotlin across Android, iOS, and desktop — commonMain @Composables, expect/actual, source-set placement, native interop, multiplatform ViewModel/navigation/Koin. NOT a single-platform native build (that is kotlin-android / swift-ios), and NOT Dart/Flutter cross-platform UI…
cmp-firebase-connect
Add Firebase to a create-cmp app and wire it to its OWN real Firebase project. Use this when the user wants Firebase in their app, or asks "add firebase", "connect my app to firebase", "set up google-services.json", "wire firebase", "create a firebase project for this app", "replace the mock firebase config", "get a…
add-feature
Add a new conforming vertical-slice feature (Screen + ViewModel + UseCase + Repository + spec + tests + golden tree + nav route + DI wiring) to this Compose Multiplatform app, cloned deterministically from the project's configured exemplar feature (qa/approvals.json's exemplarFeature — home by default). Use this when…
cmp-audit
Adversarial audit of one subsystem of a Kotlin/Compose Multiplatform app against its spec AND against platform semantics — the class of defect desktop-tier tests cannot see (alarms, notifications, PendingIntents, reboot, process death, DST). Use this when the user says "audit the notifications", "double check X for…
add-screen
Add a presentation-only slice — Screen + ViewModel + tests + golden tree + spec + nav route — for an EXISTING entity/repository in this Compose Multiplatform app, cloned deterministically from the project's configured exemplar feature's presentation layer (qa/approvals.json's exemplarFeature — home by default).…
add-repository
Add a data/domain slice ONLY — model, repository interface + impl, use case, and a hand-written fake — to this Compose Multiplatform app, cloned deterministically from the project's configured exemplar feature's data layer (qa/approvals.json's exemplarFeature — home by default). No screen, no ViewModel, no nav route…