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 agentmods add skills/demodev-lab/claude-code-plugin-demokit/gradlenpx skills add demodev-lab/claude-code-plugin-demokit --skill gradlegit clone --depth 1 https://github.com/demodev-lab/claude-code-plugin-demokitWrote 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/demodev-lab/claude-code-plugin-demokit/gradle)<a href="https://agentmods.dev/skills/demodev-lab/claude-code-plugin-demokit/gradle"><img src="https://agentmods.dev/badge/skills/demodev-lab/claude-code-plugin-demokit/gradle.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 | $0.00050 | $0.00419 |
| Opus 5 | $0.00025 | $0.00210 |
| Sonnet 5 | $0.00010 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
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 4d 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.
What it actually says
/gradle - 의존성 관리
help
인자가 help이면 아래 도움말만 출력하고 실행을 중단한다:
/gradle — Gradle 의존성 관리
사용법:
/gradle {action} [dependency]
하위 명령:
add 의존성 추가
remove 의존성 제거
check 누락된 필수/권장 의존성 체크
update 버전 업데이트 안내
예시:
/gradle add spring-boot-starter-validation
/gradle remove querydsl
/gradle check
/gradle update
관련 명령:
/init — 프로젝트 초기화
/docker — Docker 설정 생성
실행 절차
- build.gradle 분석: 현재 의존성 목록 파악
- 작업 수행:
add: 의존성 추가 + 올바른 scope (implementation/testImplementation/annotationProcessor)remove: 의존성 제거check: 누락된 필수/권장 의존성 체크update: 버전 업데이트 안내
- QueryDSL 의존성 추가 시:
io.github.openfeign.querydsl:querydsl-jpa:6.12(OpenFeign fork)io.github.openfeign.querydsl:querydsl-apt:6.12:jpa(annotationProcessor)com.querydsl사용 금지 안내
- 필수 의존성 안내: spring-boot-starter-web, data-jpa, validation, lombok
관련 Agent
- infra-expert (Phase 3)
What ships with it
1 file 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.
- 4d ago First seen · 49 lines · 50 tokens per session scan A a994024ea6ae
gradle is a skill published in the GitHub repository demodev-lab/claude-code-plugin-demokit (2 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 419 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…