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 verified-emailgit 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/verified-email)<a href="https://agentmods.dev/skills/talissonvitorino/kmp-ios-skills/verified-email"><img src="https://agentmods.dev/badge/skills/talissonvitorino/kmp-ios-skills/verified-email/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/verified-email"><img src="https://agentmods.dev/badge/skills/talissonvitorino/kmp-ios-skills/verified-email.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.04127 |
| Opus 5 | $0.00030 | $0.02063 |
| Sonnet 5 | $0.00012 | $0.00825 |
| Haiku 4.5 | $0.00006 | $0.00413 |
Grade A, and why
verified-email 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 11d 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.
This is a copy
100% identical to verified-email — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fundamentals
- Overview of Digital Credentials: Learn about cryptographically verifiable documents and the role of Credential Manager.
- Glossary : Definitions for
dcql_query,UserInfoCredential, andGetDigitalCredentialOption.
Standards & Examples
- OpenID4VP Standard: The specification used to create digital credentials requests.
- Digital Credentials Demo: Example requests and cross-platform testing tool.
- W3C Verifiable Credentials: The data model for cryptographically secured claims.
- SD-JWT: Selective Disclosure JSON Web Token format used for responses.
- mdoc: ISO/IEC 18013-5 standard for mobile documents.
Requirements
- SDK Version: Minimum SDK 28 (Android 9) is required.
- GMS Version: Google Play services version 25.49.x or higher.
Use Cases
Email verification is applicable for the following use cases:
- Account Creation/Sign-up: Remove friction by skipping manual email verification.
- Account Recovery: Securely verify email ownership during recovery flows.
- Re-authentication: Versatile verification for high-risk actions, independent of the initial sign-in method.
Limitations & Nuances
- Workspace Accounts: Google does not issue verifiable credentials for Google Workspace Accounts.
- Freshness: For [email protected] addresses, Google verifies the email at account creation but there is no freshness claim; implement an additional challenge like an OTP.
Scope & Pre-requisites
Crucial : This skill focuses exclusively on the Android client-side integration . It does not implement the app's server-side cryptographic validation logic. Server-side validation of the returned credential is required for security and must be implemented in your backend.
What ships with it
7 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.
- references/android/identity/credential-manager/index.md 5.2 KB
- references/android/identity/digital-credentials/credential-verifier.md 6.4 KB
- references/android/identity/digital-credentials/email-verification-implementation.md 13 KB
- references/android/identity/digital-credentials/email-verification.md 8.8 KB
- references/android/identity/digital-credentials/index.md 7.0 KB
- references/android/identity/passkeys/create-passkeys.md 19 KB
- references/android/identity/sign-in/credential-manager-webview.md 3.8 KB
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.
- 11d ago First seen · 423 lines · 60 tokens per session scan A 855b234d520c
verified-email is a skill published in the GitHub repository TalissonVitorino/kmp-ios-skills (12 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 4,127 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to verified-email, differing in 11 lines, and is treated as a copy.
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-new
Scaffold a new MOBILE app — Android + iOS from one Kotlin/Compose Multiplatform codebase — from a bare "create a mobile app" to a green, verified build. Guardrails first: if the user already chose a different framework (React Native, Expo, Flutter, SwiftUI, native), do NOT redirect them here; if they only asked a…
cmp-firebase-connect
Wire a freshly scaffolded CMP/KMP app to its OWN real Firebase project — the #1 post-scaffold manual step. Use this when the user wants to connect their app to Firebase, or asks "connect my app to firebase", "set up google-services.json", "wire firebase", "create a firebase project for this app", "replace the…
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-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…
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).…