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 skills add Promastergame/tinyapk-lab --skill proguardgit clone --depth 1 https://github.com/Promastergame/tinyapk-labWrote 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/promastergame/tinyapk-lab/proguard)<a href="https://agentmods.dev/skills/promastergame/tinyapk-lab/proguard"><img src="https://agentmods.dev/badge/skills/promastergame/tinyapk-lab/proguard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/promastergame/tinyapk-lab/proguard"><img src="https://agentmods.dev/badge/skills/promastergame/tinyapk-lab/proguard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 73 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.1 | $0.00041 | $0.02506 |
| Opus 5.5 | $0.00016 | $0.01002 |
| Sonnet 5.5 | $0.00008 | $0.00501 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
proguard-r8-without-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: ProGuard / R8 Without Gradle
Key insight: R8 is already inside d8.jar!
You do NOT need to download ProGuard or R8 separately. Google's R8 compiler (which replaced ProGuard in all modern Android builds) is bundled inside d8.jar from the Android SDK build-tools. Same jar, different main class:
# D8 mode — just converts .class → .dex (no shrinking)
java -cp d8.jar com.android.tools.r8.D8 ...
# R8 mode — shrinks + obfuscates + converts .class → .dex
java -cp d8.jar com.android.tools.r8.R8 ...
R8 does everything ProGuard does plus DEX conversion in one step — no separate ProGuard pass needed.
What R8 does
| Feature | Result |
|---|---|
| Tree shaking | Removes unused classes, methods, fields |
| Obfuscation | Renames classes/methods to a, b, c... |
| Minification | Removes debug info, line numbers |
| DEX conversion | Outputs classes.dex directly |
Typical size reduction on a real app: 30-50%. On already-minimal apps (like a 16KB Tetris): 15-27% — most of the weight is APK structure and signing overhead.
ProGuard config file
Create proguard.pro — tells R8 what to keep (don't obfuscate entry points):
# Keep all Android entry points
-keep public class * extends android.app.Activity
-keep public class * extends android.app.Service
-keep public class * extends android.view.View
-keep public class * extends android.view.SurfaceView
# Keep lifecycle methods on Activities
-keepclassmembers class * extends android.app.Activity {
protected void onCreate(android.os.Bundle);
protected void onDestroy();
protected void onPause();
protected void onResume();
protected void onActivityResult(int, int, android.content.Intent);
}
# Keep SurfaceView callbacks
-keepclassmembers class * extends android.view.SurfaceView {
public void surfaceCreated(android.view.SurfaceHolder);
public void surfaceDestroyed(android.view.SurfaceHolder);
public void surfaceChanged(android.view.SurfaceHolder, int, int, int);
public boolean onTouchEvent(android.view.MotionEvent);
}
# Keep View constructors (needed for inflation)
-keepclassmembers class * extends android.view.View {
public <init>(android.content.Context);
public <init>(android.content.Context, android.util.AttributeSet);
}
# Don't warn about missing classes from android.jar stubs
-dontwarn **
# Allow R8 to make members more accessible for optimization
-allowaccessmodification
# Skip preverification (not needed for Android/DEX)
-dontpreverify
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.
- 1mo ago First seen · 287 lines · 41 tokens per session scan A 77792c3acde2
proguard-r8-without-gradle is a skill published in the GitHub repository Promastergame/tinyapk-lab (25 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,506 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
analyzing-android-malware-with-apktool
Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination detection, and identification of obfuscated code, dynamic code loading, and reflection-based API calls. Use to statically…
analyzing-android-malware-with-apktool
Use when perform static analysis of Android APK malware samples using apktool for decompilation, jadx for Java source recovery, and androguard for permission analysis, manifest inspection, and suspicious API call detection. Use when performing static analysis of android apk malware samples using apktool.
android-reverse-engineering
Decompile Android APK, XAPK, JAR, and AAR files using jadx or Fernflower/Vineflower. Reverse engineer Android apps, extract HTTP API endpoints, trace call flows from UI to network layer, and analyze runtime behavior with Frida, network capture, JNI/SO inspection, and signature generation. Use when the user wants to…
create-patch
Create or continue an authorized Morphe Android patch from an APK and requested change. Use when the user wants the complete workflow: APK reconnaissance, decompilation, target discovery, smali verification, patch implementation, and local validation.
find-patch-targets
Find Morphe patch targets in decompiled Android source and verify each target against exact smali bytecode. Use after decompiled source and smali exist.
recon-apk
Inspect an authorized APK, APKM, APKS, or XAPK and create a structured Morphe reconnaissance report. Use for a new app before decompilation or patch target analysis.