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 gaelic-ghost/socket --skill gradle-agp-workflowgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/gradle-agp-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/gradle-agp-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/gradle-agp-workflow/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/gaelic-ghost/socket/gradle-agp-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/gradle-agp-workflow.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.00074 | $0.01093 |
| Opus 5.5 | $0.00030 | $0.00437 |
| Sonnet 5.5 | $0.00015 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
gradle-agp-workflow 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 1mo 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Gradle And AGP Workflow
Purpose
Keep Android build, dependency, variant, and packaging work grounded in the repository's real Gradle and Android Gradle Plugin configuration.
The practical decision is which Gradle files own the change, which Android modules and variants are affected, and which command proves the change without relying on machine-global state.
Source Check
Use repo-local Gradle files, checked-out dependency sources, and Dash.app Gradle or Java docsets opportunistically. Use official documentation as authority for Android-specific and version-sensitive behavior:
- Android build documentation
- Android Gradle Plugin release notes
- Gradle User Manual
- Gradle Java Toolchains
- Kotlin Gradle plugin documentation
Translate documentation into concrete Gradle files, module names, variants, and commands.
Inspection Workflow
- Identify the Gradle owner:
settings.gradleorsettings.gradle.kts- root
build.gradleorbuild.gradle.kts - module
build.gradleorbuild.gradle.kts gradle/libs.versions.tomlgradle.propertiesgradle/wrapper/gradle-wrapper.properties
- Identify Android plugin shape:
com.android.applicationcom.android.librarycom.android.test- Kotlin Android plugin aliases or IDs
- Inspect toolchain and SDK policy:
- AGP version
- Gradle wrapper version
- Kotlin plugin version
- Java toolchain or source/target compatibility
compileSdk,minSdk, and target SDK policy
- Inspect variants and packaging:
- build types
- product flavors
- signing configs
- namespace and application ID
- app bundles, APKs, ProGuard/R8, and generated outputs
- Inspect dependencies:
- version catalogs
- plugin management
- dependency constraints
- repositories
- generated sources, annotation processors, KSP, KAPT, or codegen plugins
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.
- 1mo ago First seen · 122 lines · 74 tokens per session scan A e90da9b23f7b
gradle-agp-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,093 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-08-31.
Other skills, from other repositories
app-store-optimization
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
flutter-screenshots
Automate App Store & Google Play screenshot generation for Flutter apps. Scans routing and screens, scores high-value marketing screens, generates self-contained mock harness, runs native simulator captures (iPhone 6.9", iPad 13", Android Phone/Tablet), strips alpha channels, and validates exact store resolutions.
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
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.
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.