android-modularization

A guide for splitting a large Android repository into separate modules for features, shared core code, and build configuration. A monorepo is one repository containing multiple parts of a project; these modules keep those parts organized and prevent circular dependencies.

In plain words
What is it for?
Use it to plan feature and core modules, organize shared build logic, split an Android project, and remove cyclic module dependencies.
Why use it?
It makes project boundaries clearer and helps stop modules from depending on one another in loops that are hard to build and maintain.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/krutikjain/android-agent-skills/android-modularization
Clone the repo
git clone --depth 1 https://github.com/krutikJain/android-agent-skills

Made for: Claude Code.

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 74 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00074
Opus 5 $0.00012 $0.00037
Sonnet 5 $0.00005 $0.00015
Haiku 4.5 $0.00002 $0.00007

Measured 2d ago against content hash ce810abf2990, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

android-modularization 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 2d 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.

.claude/agents/android-modularization.md · 11 lines

What it actually says

android-modularization

Use this subagent when the request is about android module split, feature modularization in android, break cyclic module dependency.

Canonical source: skills/android-modularization/SKILL.md.

Changes

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.

  1. 2d ago First seen · 11 lines · 24 tokens per session scan A ce810abf2990

Subscribe to this mod's changes

android-modularization is an agent published in the GitHub repository krutikJain/android-agent-skills (14 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 74 once invoked, about $0.0001 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.