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 limrun-inc/skills --skill limrun-gradlegit clone --depth 1 https://github.com/limrun-inc/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/limrun-inc/skills/limrun-gradle)<a href="https://agentmods.dev/skills/limrun-inc/skills/limrun-gradle"><img src="https://agentmods.dev/badge/skills/limrun-inc/skills/limrun-gradle/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/limrun-inc/skills/limrun-gradle"><img src="https://agentmods.dev/badge/skills/limrun-inc/skills/limrun-gradle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00128 | $0.02500 |
| Opus 5 | $0.00064 | $0.01250 |
| Sonnet 5 | $0.00026 | $0.00500 |
| Haiku 4.5 | $0.00013 | $0.00250 |
Grade A, and why
limrun-gradle 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 9d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Gradle build
Build Android projects on Limrun's remote Gradle sandboxes, from any
environment (Linux, Windows, macOS, VM, container). lim gradle build syncs
your sources to a remote instance, runs the project's own Gradle wrapper
there, and streams the build output. Never fall back to local Gradle, a local
Android SDK, or a local emulator. Your job doesn't end at a green build: get
the app running or the artifact delivered, and iterate until the user is
satisfied.
For iOS builds, use limrun-xcode instead of this skill. For the Expo
dev-client loop (Metro, hot reload) on either platform, use
limrun-expo-development; it comes back here for the Android Debug
build.
Auth and CLI
Install if needed: npm install --global lim. Auth is lim login or
LIM_API_KEY (it may be set outside the project, so don't ask for it just
because it's missing from .env or the shell). The CLI is the source of truth:
the commands in this skill are verified, but if a flag errors or you need one
not shown here, check --help instead of guessing:
lim gradle --help
lim gradle build --help
Build an APK
Instead of ./gradlew, build with:
lim gradle build .
This creates or reuses the remembered Gradle instance, syncs the current
directory, and runs assembleDebug by default. Pick tasks explicitly with
--task (repeatable):
lim gradle build . --task :app:assembleRelease
Use --project-path when the Gradle root is nested and auto-discovery is
ambiguous (for example a bare React Native repo where Gradle lives in
android/; the server usually finds it on its own):
lim gradle build . --project-path android
Expo managed-workflow projects (no android/ directory) are detected
automatically: the sandbox installs dependencies and runs expo prebuild
before Gradle. Setting --expo-app-dir (monorepos) or --abi forces that
pipeline and errors when no Expo app is detected:
lim gradle build ./my-monorepo --expo-app-dir apps/mobile
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.
- 9d ago First seen · 232 lines · 128 tokens per session scan A 44de67da5488
limrun-gradle is a skill published in the GitHub repository limrun-inc/skills (1 stars, last pushed today), licensed MIT. It adds 128 tokens to every session and 2,500 once invoked, about $0.0006 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
slipstream-inspector
This skill should be used when the user asks to "run the Flutter app", "flutter run", "start the app", "launch the app", "test the UI", "take a screenshot of the app", "click a button in the app", "debug the layout", or any request involving launching, observing, or interacting with a running Flutter app. When the…
dart-flutter-patterns
Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
liquid-glass-design
Patterns for implementing Apple's Liquid Glass — a dynamic material that blurs content behind it, reflects color and light from surrounding content, and reacts to touch and pointer interactions. Covers SwiftUI, UIKit, and WidgetKit integration.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
android-clean-architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
compose-multiplatform-patterns
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.