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 ingest-gradle-upgradegit 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/ingest-gradle-upgrade)<a href="https://agentmods.dev/skills/rnett/gradle-mcp/ingest-gradle-upgrade"><img src="https://agentmods.dev/badge/skills/rnett/gradle-mcp/ingest-gradle-upgrade/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/ingest-gradle-upgrade"><img src="https://agentmods.dev/badge/skills/rnett/gradle-mcp/ingest-gradle-upgrade.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.00279 | $0.05663 |
| Opus 5 | $0.00139 | $0.02831 |
| Sonnet 5 | $0.00056 | $0.01133 |
| Haiku 4.5 | $0.00028 | $0.00566 |
Grade A, and why
ingest-gradle-upgrade scanned grade A with 1 finding 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Enumerate the reading set.** Fetch the official versions metadata — `curl.exe -s https://services.gradle.org/versions/all` (JSON array; the same `services.gradle.org` host this repo already uses for `versions/curren How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest Gradle Upgrade
Post-upgrade maintenance process for this repository. After the Gradle wrapper version is bumped, ingest the release notes, upgrade guides, and linked documentation for the new version, then update (a) this repo's code and tooling, (b) the shipped Gradle MCP skills under src/main/skills/, and (c) the generated best-practices corpus, so everything stays accurate for the new version.
More info: Do all documentation research through gradle_docs pinned to explicit versions: gradle_docs(path="release-notes.md", version="<v>"), gradle_docs(path="userguide/upgrading_version_<N>.md", version="<v>"), and gradle_docs(query="tag:<scope> <term>", version="<v>") with scopes userguide, dsl, release-notes, best-practices, upgrading, javadoc, samples. Version resolution is explicit version → wrapper auto-detection via projectRoot → latest stable; always pass version explicitly here, because old and new behavior must be distinguished. Use gradle_docs(path=".", version="<v>") to list a version's doc page tree. Sourcing boundary: release enumeration (which versions exist and must be read) comes from the official versions metadata endpoint https://services.gradle.org/versions/all (workflow step 2.1) and supplies version metadata only; all documentation content is read exclusively through gradle_docs.
Before You Start
- Confirm the wrapper bump exists (or is part of this task):
gradle/wrapper/gradle-wrapper.propertiesdiffers from the last recorded version. - Establish the OLD version before reading anything — git history of the wrapper properties file is the only reliable source (Workflow step 1).
- Plan for both halves up front: (a) repo code/tooling and (b) shipped skills. Neither half is optional; a "no impact" conclusion for either still requires explicit triage evidence in the ledger.
Scope
In scope:
- This repo's own code and tooling: build scripts, the Tooling API layer, init scripts, docs/version services, tests.
- Shipped skills under
src/main/skills/: SKILL.md bodies, references, compatibility tables, lifecycle language, andgradle_docspointers. - The generated best-practices corpus — regenerated, never hand-edited.
- Records: wrapper version line in
.junie/playbook.md;Build Verificationrecord inAGENTS.md.
What ships with it
2 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.
- 13d ago First seen · 174 lines · 279 tokens per session scan A 290a66d74d33
ingest-gradle-upgrade is a skill published in the GitHub repository rnett/gradle-mcp (60 stars, last pushed 5d ago), licensed Apache-2.0. It adds 279 tokens to every session and 5,663 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
trace-mcp-codemod
Use trace-mcp applycodemod for any bulk mechanical change instead of repeated Edit calls. Activate whenever the same edit pattern would be applied 2+ times, across one file or many.
entity-design
Design EF Core entities with navigation properties, value objects, Fluent API configuration, and audit fields. Use when creating new database entities, adding relationships, configuring owned types, designing a domain model for Entity Framework Core, or setting up table-per-hierarchy inheritance.
create-migration
Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.
tech-preflight-dotnet
Verify .NET SDK compatibility, map project dependency graphs, and run baseline builds before code changes. Use when starting a new task, onboarding to a .NET solution, checking environment readiness, or diagnosing build failures from SDK mismatches.
go-rust-reverse
Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.