Borrowing it
Nothing to install: this file belongs to code-payments/code-android-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/code-payments/code-android-app/code/cash/.claude/skills/propose-analytics-event/SKILL.mdgit clone --depth 1 https://github.com/code-payments/code-android-appWrote 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/code-payments/code-android-app/propose-analytics-event)<a href="https://agentmods.dev/skills/code-payments/code-android-app/propose-analytics-event"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/propose-analytics-event/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/code-payments/code-android-app/propose-analytics-event"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/propose-analytics-event.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.00064 | $0.02130 |
| Opus 5.5 | $0.00026 | $0.00852 |
| Sonnet 5.5 | $0.00013 | $0.00426 |
| Haiku 4.5 | $0.00006 | $0.00213 |
Grade A, and why
propose-analytics-event 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 today.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propose an analytics event
The person asking is usually not an engineer. They know what they want to measure, not how the app is built. Your job is to turn that into a catalogue change an engineer can review and wire up, in a draft pull request, without making them touch git, Kotlin, or Gradle.
The catalogue is libs/analytics-events/events.toml. Its header explains every field: read it
first. Both apps send events from this one file (iOS through the shared KMP package), so a
proposal here covers Android and iOS.
Talk like this
Say screens, taps, and numbers. Never make the person deal with files, builders, Gradle, the "share sheet", SharedCore, or KMP. If you must name an event, give its Mixpanel name.
| Instead of | Say |
|---|---|
"add an [[event]] to events.toml" |
"add a new event to the list both apps send" |
| "wire the call site" | "an engineer connects it to the button" |
| "share sheet" | "the phone's Share menu" |
| "property" | "a detail recorded with it, like which method they picked" |
| "Publish SharedCore" | "it reaches iPhone in a later release" |
1. Set up quietly
Run git fetch origin and git switch -c feat/analytics-<short-slug> origin/code/cash. The base
branch is code/cash. There is no main. Don't ask the person anything about this step.
2. Ask before you build
Ask one question at a time, and offer concrete choices taken from the real app (read the screen's code to find them). Start each ask with question 1, then sort it with step 3. Only asks that end up as new or changed events need questions 2 to 4. Don't edit anything until those asks have all four answers:
- The question behind it. "What will you decide or report with this number?" Their answer tells you whether an event is the right tool at all.
- The exact moment. What they see and tap, and whether it counts attempts ("tapped Share") or completions ("the card was sent"). Words like "share", "engaged", "uses" and "converts" have several meanings. List the ones the app supports and let them pick. Check for other paths to the same outcome (a second share button, a share-to-chat screen).
- Breakdowns. What they'd filter by in Mixpanel: method, source, success/failure.
- Both apps? The default is yes.
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.
- today First seen · 156 lines · 64 tokens per session scan A 986e6dcbdb99
propose-analytics-event is a skill published in the GitHub repository code-payments/code-android-app (23 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,130 once invoked, about $0.0003 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-30.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
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.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp: publish the Windows head first, then point packaging at the resolved resizetizer manifest. Use for a MAUI MSIX or signed unpackaged build, MAUI packaging in CI, or 'manifest contains unresolved placeholders' errors from winapp package.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.