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 agentmods add rules/arindamxd/camerax-android/play-console-release-notesgit clone --depth 1 https://github.com/arindamxd/camerax-androidWhat 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 | $0.00000 | $0.00456 |
| Opus 5 | $0.00000 | $0.00228 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
play-console-release-notes 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 3d 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.
What it actually says
Play Console release notes
When the user asks for Play Store / Play Console release notes (or shipping a version), draft both:
- Release name —
versionNameonly (e.g.1.7.0), ≤50 characters. Not shown to users. - Release notes — prefer the long bullet form below (not the one-line summary). Wrap in language tags for Play Console paste.
Always output both fields together, e.g. Release name: 1.7.0 then the <en-US> block.
Preferred format (long)
Release name: {versionName}
<en-US>
What's new in CameraX {versionName}
• {user-facing highlight}
• {user-facing highlight}
• {user-facing highlight}
• {user-facing highlight}
• Stability and performance improvements
</en-US>
Rules
- Lead with
What's new in CameraX {versionName}. - Use 4–6 short bullets of user-visible changes (modes, capture formats, gallery, Settings, UI). Skip architecture, DI, KDoc, agent docs, and build-only churn.
- Source content from
git logsince the previous tag, README.md feature table, and RELEASE.md shipping version (versionMajor/Minor/Patchin rootbuild.gradle.kts). - Prefer device-gated wording when needed (“when your device supports them”).
- End with a stability / polish bullet when the release includes fixes or UI cleanup.
- Paste-ready: include
<en-US>…</en-US>tags. Add other locales only if asked. - Do not invent features that are not in the shipping tree.
Avoid
<en-US>
CameraX 1.7.0: Slo-mo, Effects… UI polish and fixes.
</en-US>
One-liners are a fallback only if the user explicitly asks for a shorter option.
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.
- 3d ago First seen · 51 lines · 0 tokens per session scan A 4eb5212899ac
play-console-release-notes is a cursor rule published in the GitHub repository arindamxd/camerax-android (132 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 456 tokens. 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 cursor rules, from other repositories
cursorrules
You are an expert in SceneView, the #1 open-source 3D & AR SDK for Android and iOS.
compose-accessibility
Compose accessibility rules for TalkBack — icons, headings, Canvas, live regions, focus, modals, and attribute preservation.
testing-conventions
Testing conventions — JUnit 4, Kotest property tests, instrumented tests, what to test when.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
ios-viewmodel
ViewModels conform to ObservableObject and expose state via @Published properties.
compose-ui
Compose UI conventions — Material 3, recomposition optimization, Compose-only UI, theming.