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 GDvega/super-android-kotlin-firebase-skill --skill workmanager-background-syncgit clone --depth 1 https://github.com/GDvega/super-android-kotlin-firebase-skillWrote 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/gdvega/super-android-kotlin-firebase-skill/workmanager-background-sync)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/workmanager-background-sync"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/workmanager-background-sync.svg" alt="Measured on agentmods" 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.00029 | $0.00636 |
| Opus 5 | $0.00015 | $0.00318 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
workmanager-background-sync 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Implement reliable Android background work without leaking scopes, draining battery or duplicating sync jobs.
When to use
- Scheduling background sync.
- Uploading data when network returns.
- Adding periodic or one-time WorkManager jobs.
- Testing retry and backoff behavior.
- Designing offline-first synchronization.
Inputs to inspect
- Worker classes
- Repository and Room transaction boundaries
- Network layer and DTO mapping
- DI setup for workers
AndroidManifest.xmlpermissions- Existing sync scheduler code
Required workflow
- Define the sync contract and idempotency key.
- Choose one-time or periodic work with constraints.
- Keep work inside structured coroutine APIs.
- Persist progress and retry safely.
- Add unit tests for success, retry and failure.
Rules
- Do not use
GlobalScope. - Do not create unnecessary Services.
- Do not run infinite loops inside Workers.
- Use constraints for network/battery when relevant.
- Make sync idempotent and retry-safe.
Related existing skills
Local skills to invoke
- room-datastore
- networking-retrofit-ktor
- firebase-core
- testing
External companion skills to use when installed
Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.
- android/skills — use for official Android workflow alignment when a first-party companion skill exists for the task.
Files commonly touched
*Worker.ktSyncScheduler.kt- Repository and DAO files
- DI modules
AndroidManifest.xml- Worker tests
Commands to validate
./gradlew test
./gradlew assembleDebug
Common mistakes to avoid
- Scheduling duplicate unique work.
- Retrying non-idempotent uploads.
- Doing long foreground work without notification requirements.
- Ignoring process death and app restart.
Checklist
- Constraints chosen.
- Unique work policy documented.
- Backoff configured.
- Sync idempotent.
- Worker tests added or recommended.
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.
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.
- 8d ago First seen · 108 lines · 29 tokens per session scan A 659f45c3d2d3
workmanager-background-sync is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 636 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
maui-unit-testing
Add MAUI app tests around ViewModels, services, platform abstractions, and unit/integration/device boundaries. USE FOR: xUnit, avoiding MauiProgram.CreateMauiApp in unit tests, fakes/mocks, injectable Essentials interfaces, PlatformNotSupportedException, navigation/data services, AppProjectReference, device-test…
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
ios-testing
Testing patterns for Swift and SwiftUI apps.
mobile-testing
Android and JVM testing - JUnit5, MockK, Turbine for Flow, and Compose UI testing for unit, integration, and UI tests; also applies to KMP commonTest running on the JVM/Android target. For iOS/Swift tests (XCTest, Swift Testing, XCUITest) use ios-testing. For TDD methodology and the three-tier test model (fake-first…
flutter-testing
A testing guide for Flutter mobile apps and NestJS backends used across multiple regions. It covers unit tests, screen tests, end-to-end tests, regional build variants called flavors, and rules for testing payments, tenants, and external services with test doubles.
Android Testing
JUnit + Robolectric unit tests, Compose UI tests, screenshot tests, and Espresso for legacy views.