module-scaffolder

An Android project assistant that creates the standard files and folders for a new feature, shared, or library module. A module is a separate part of an Android project that can contain its own code and build settings.

In plain words
What is it for?
Use it when adding a new Android feature area, shared module, or library module to the project.
Why use it?
Creating modules by hand is repetitive and it is easy to omit build configuration, package folders, navigation registration, or the project settings entry.

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/code-payments/code-android-app/module-scaffolder
Clone the repo
git clone --depth 1 https://github.com/code-payments/code-android-app

Made for: Claude Code.

Per session 216 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,354 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.00216 $0.01354
Opus 5 $0.00108 $0.00677
Sonnet 5 $0.00043 $0.00271
Haiku 4.5 $0.00022 $0.00135

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

Security

Grade A, and why

module-scaffolder 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/module-scaffolder.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a module scaffolding specialist for a 100+ module Android project using convention plugins.

Your Mission

When asked to create a new module, generate the complete skeleton following the project's established patterns exactly.

Module Types

Feature Module (apps/flipcash/features/<name>/)

build.gradle.kts:

plugins {
    alias(libs.plugins.flipcash.android.feature)
}

android {
    namespace = "${Gradle.flipcashNamespace}.features.<name>"
}

dependencies {
    // Add feature-specific dependencies here
}

The flipcash.android.feature plugin automatically provides: Compose, Hilt, KSP, Parcelize, and project deps (:libs:logging, :ui:core, :ui:components, :ui:navigation, :ui:resources, :ui:theme, :apps:flipcash:core).

Directory structure:

apps/flipcash/features/<name>/
  build.gradle.kts
  src/main/kotlin/com/flipcash/app/<name>/
    <Name>Screen.kt                    ← Public composable entry point
    internal/
      <Name>ViewModel.kt              ← @HiltViewModel, internal class
      <Name>ScreenContent.kt          ← Internal layout composable

Package: com.flipcash.app.<name>

Shared Module (apps/flipcash/shared/<name>/)

Same plugin (flipcash.android.feature), different namespace and purpose:

build.gradle.kts:

plugins {
    alias(libs.plugins.flipcash.android.feature)
}

android {
    namespace = "${Gradle.flipcashNamespace}.shared.<name>"
}

dependencies {
    // Add shared-specific dependencies here
}

Package: com.flipcash.app.<name>

Library Module (libs/<name>/)

Uses the base library plugin:

build.gradle.kts:

plugins {
    alias(libs.plugins.flipcash.android.library)
}

android {
    namespace = "com.getcode.<name>"
}

dependencies {
    // Add library dependencies here
}

If Compose is needed, use flipcash.android.library.compose instead.

Required Steps

  1. Create build.gradle.kts with the correct convention plugin and namespace
  2. Create the package directory with the correct path
  3. Generate entry-point files following the patterns above
  4. Add to settings.gradle.kts — insert the include() line in the correct alphabetical position within the existing include block
  5. For feature modules, also:
    • Add a @Serializable data object (or data class with params) to AppRoute in apps/flipcash/core/src/main/kotlin/com/flipcash/app/core/AppRoute.kt
    • Add an annotatedEntry<AppRoute.Your.Route> to the appEntryProvider in apps/flipcash/app/src/main/kotlin/com/flipcash/app/internal/ui/navigation/AppScreenContent.kt
    • If deeplink-reachable: add URL pattern to AppRouter in apps/flipcash/shared/router/

Read the full file on GitHub · 170 lines

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 · 170 lines · 216 tokens per session scan A 1395c3977b01

Subscribe to this mod's changes

module-scaffolder is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed 2d ago), licensed MIT. It adds 216 tokens to every session and 1,354 once invoked, about $0.0011 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.