lean-mobile
Skill2 starsChanged 56 days agoMITView on GitHub
Runs token-efficient defensive mobile app reviews for Cursor and Codex. Inventories exported Android components, backup flags, ATS exceptions, and deep links in local manifests and plists, then reports compact hardening fixes. Use when the user asks for Android, iOS, mobile security, deep links, or certificate pinning review. Do not use for jailbreak exploits, store bypasses, or attacking other apps.
In this repository21 other files it gives its agents.
- lean-cryptoSkill
- lean-privacySkill
- lean-secSkill
- lean-webSkill
- lean-a11ySkill
- lean-depsSkill
- lean-docsSkill
- lean-perfSkill
- lean-reviewSkill
- lean-ciSkill
- lean-cloudSkill
- lean-costSkill
- lean-hardeningSkill
- lean-iotSkill
- lean-netSkill
- lean-dfirSkill
- lean-ir-playbookSkill
- lean-malwareSkill
- lean-osintSkill
- lean-phishSkill
- lean-threat-modelSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Run manifest. Queue exported activities, backup=true, cleartext traffic, ATS exceptions, custom URL schemes.
- Distinctive: line 45
No Frida/objection attack recipes.
- Distinctive: line 46
Do not print signing keys or keystore passwords.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lean Mobile
Defensive review of manifests and app config in this workspace, not of devices you do not own.
Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.
python3 "$SKILL_ROOT/scripts/lean_mobile.py" manifest .
python3 "$SKILL_ROOT/scripts/lean_mobile.py" trim --chars 2500 path/to/out.txtMode
Default lean.
| Mode | Budget |
lean | manifest + up to 8 slices; references/android.md; ≤6 findings |
standard | + references/ios.md; up to 16 slices; ≤10 findings |
deep | needed refs only; ≤16 findings |
Workflow
- Run
manifest. Queue exported activities, backup=true, cleartext traffic, ATS exceptions, custom URL schemes. - Slice-read the XML/plist. Cap quotes at 12 lines.
- Report the safer flag. Stop unless asked to patch.
Hard rules
- Workspace files only. No sideloading malware or store circumvention.
- No Frida/objection attack recipes.
- Do not print signing keys or keystore passwords.
Report template
## Lean-mobile (`<mode>`)
**App:** <package> | **Budget:** files_read=<n>
| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | AndroidManifest.xml | exported activity | exported=false or permission |Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.