metamodulelisted
Install: claude install-skill yspbwx2010/skills
# Metamodule
A metamodule is a **special root module that provides the module system's mounting and installation
backend**. Regular modules ship `system/` files and scripts; a metamodule decides *how* those files
get mounted over `/system` and *how* modules install. KernelSU moved this out of its core so the
mount strategy is pluggable (overlayfs, magic mount, FUSE, or none) and KernelSU itself performs no
mounts — a smaller detection surface. **Without a metamodule installed, KernelSU mounts nothing.**
This is a **KernelSU** concept (the official reference impl is `meta-overlayfs`); **APatch** adopted
the same design, so a metamodule is largely portable between them. This skill is verified against
KernelSU's `ksud` source and the official metamodule guide, with APatch's `apd` differences called
out. It is **not** the guide for ordinary modules (those ship `system/` + scripts and need no
`metamodule=1`) — this is only for building the mount/install backend itself.
## What makes a module a metamodule
One line in `module.prop`:
```txt
id=meta-example
name=My Metamodule
version=1.0
versionCode=1
author=you
description=Custom mount backend
metamodule=1
```
- **`metamodule=1`** (or `metamodule=true`, case-insensitive) is the only thing that distinguishes a
metamodule from a regular module. Without it, it's treated as a regular module.
- **Name the id `meta-*`** by strong convention (`meta-overlayfs`, `meta-magicmount`, …) so users and
the manager recognize it and it won'