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 rnett/gradle-mcp --skill authoring-gradle-buildsgit clone --depth 1 https://github.com/rnett/gradle-mcpWrote 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/rnett/gradle-mcp/authoring-gradle-builds)<a href="https://agentmods.dev/skills/rnett/gradle-mcp/authoring-gradle-builds"><img src="https://agentmods.dev/badge/skills/rnett/gradle-mcp/authoring-gradle-builds/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/rnett/gradle-mcp/authoring-gradle-builds"><img src="https://agentmods.dev/badge/skills/rnett/gradle-mcp/authoring-gradle-builds.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector 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.00052 | $0.03610 |
| Opus 5 | $0.00026 | $0.01805 |
| Sonnet 5 | $0.00010 | $0.00722 |
| Haiku 4.5 | $0.00005 | $0.00361 |
Grade A, and why
authoring-gradle-builds 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 7d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gradle Build Authoring
Author or modify Gradle build definitions, build logic, project structure, and delivery wiring. Optimize for lazy, decoupled, configuration-cache-compatible builds.
Positive Triggers (when to activate)
- Authoring or modifying build.gradle(.kts), settings.gradle(.kts), convention plugins, modules, or subprojects.
- Adding or changing dependency declarations, version catalogs, repositories, or plugin management.
- Configuring JDK toolchains, Kotlin compiler options, test frameworks, publishing, or CI wiring.
- Declaring or modifying composite builds (included builds via
includeBuild, build-logic wiring). - Creating custom tasks, worker actions, build services, value sources, service injection, or project-isolation-compatible build logic.
- Assessing build health, running best-practice audits, or handling Gradle doctor / build health check / performance audit requests.
- Modifying advanced Gradle configuration and build performance settings.
Negative Triggers (when NOT to activate)
- Operation/execution (running builds, running tests, diagnosing failures, and read-only dependency inspection/update discovery) belongs to
using-gradle; authoring/modifying build definitions (including dependency declarations and version catalogs) belongs toauthoring-gradle-builds. Trivial one-line everyday dependency edits (catalog entry + declaration + version bump) are a sanctioned overlap inusing-gradle; anything structural (plugins, repositories, modules, toolchains, publishing, CI) isauthoring-gradle-buildsonly. - Researching internal Gradle APIs (use
using-gradle's research workflow). - Probing runtime project code (use
interacting-with-project-runtime). - Verifying Compose UI (use
verifying-compose-ui). - Advanced dependency engineering — variant-aware resolution diagnostics, dependency verification implementation (verification-metadata.xml authoring, PGP key and checksum workflows, verification repair, and CI verification workflows), component metadata rules, dependency substitution rules and composite-build diagnosis, capability conflicts, lock modes beyond basics, advanced version catalogs, and repository governance modes (use
advanced-gradle-dependencies). Composite-build authoring stays here. Basic dependency declaration, version-catalog basics, and basic locking stay here.
What ships with it
27 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.
- references/advanced-configuration.md 20 KB
- references/artifact-publishing.md 13 KB
- references/build-health-assessment.md 17 KB
- references/build-lifecycle.md 6.3 KB
- references/build-scans.md 7.6 KB
- references/ci-cd-builds.md 8.4 KB
- references/composite-builds.md 9.2 KB
- references/configurations-and-variants.md 11 KB
- references/continuous-builds.md 6.3 KB
- references/convention-plugins.md 6.5 KB
- references/custom-tasks.md 11 KB
- references/dependencies-and-catalogs.md 24 KB
- references/dependency-locking.md 7.4 KB
- references/extensions.md 5.1 KB
- references/file-operations.md 6.4 KB
- references/java-builds.md 7.7 KB
- references/jdk-toolchains.md 12 KB
- references/kotlin-compiler-options.md 8.8 KB
- references/kotlin-dsl.md 6.6 KB
- references/managed-types-and-providers.md 15 KB
- references/modules-and-settings.md 11 KB
- references/plugin-development.md 8.8 KB
- references/research.md 12 KB
- references/task-properties.md 5.8 KB
- references/testing-configuration.md 19 KB
- references/upgrading-and-release-notes.md 2.7 KB
- references/worker-api.md 7.1 KB
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.
- 7d ago Changed · +2 lines a831b1afec6d
- 12d ago First seen · 140 lines · 52 tokens per session scan A a2ad345ca2bc
authoring-gradle-builds is a skill published in the GitHub repository rnett/gradle-mcp (60 stars, last pushed 4d ago), licensed Apache-2.0. It adds 52 tokens to every session and 3,610 once invoked, about $0.0003 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-30.
Other skills, from other repositories
Java Patterns
Use this skill when working on Java services/libs and you want clean layering, safe null handling, predictable build structure (Maven/Gradle), and testable code.
java-best-practices
Java coding best practices. Use when writing or reviewing Java code (17+). Covers modern features, error handling, and patterns.
Build Tool Conventions
Maven/Gradle standard layout, dependency management, plugin versioning, and reproducible builds.
design-patterns
Common design patterns with Java examples (Factory, Builder, Strategy, Observer, Decorator, etc.). Use when user asks "implement pattern", "use factory", "strategy pattern", or when designing extensible components.
java-migration
Guide for upgrading Java projects between major versions (8→11→17→21→25). Use when user says "upgrade Java", "migrate to Java 25", "update Java version", or when modernizing legacy projects.
jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.