Extension System Audit
Testing & Qualityextension-system-auditExtension System Audit is an Agent Skill for testing & quality published in the oxyroid/M3UAndroid repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Audit M3UAndroid extension APIs and runtime for host/plugin boundaries, classloader compatibility, manifest metadata assumptions, IPC/protobuf compatibility, and dependency leakage.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/oxyroid/M3UAndroid/blob/HEAD/.claude/skills/extension-system-audit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/extension-system-audit, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Extension System Audit
Audit extension compatibility with evidence from API, runtime, manifest, and dependency boundaries.
When To Use
Use when a task changes or reviews:
- Extension API modules or host runtime loading
- Plugin discovery, manifest metadata, or registration
- AIDL/protobuf contracts
- Classloader behavior
- Host/plugin dependency boundaries
Required Context
Read first:
AGENTS.mdcore/AGENTS.mddocs/ai/playbooks/extension-system.md- Relevant app/business/data instructions for touched modules
- Nearby extension API, runtime, manifest, and sample/plugin code
Audit Checks
Verify with file evidence:
- API/runtime boundary is explicit and stable.
- Extension APIs do not depend on app or host implementation modules.
- Classloader assumptions are documented or guarded.
- Manifest metadata is validated and has failure behavior.
- AIDL/protobuf changes preserve compatibility or document migration.
- Host/plugin dependency leakage is not introduced.
- Public or semi-public API changes include compatibility notes.
Process
- Map extension modules, API surfaces, runtime loaders, and metadata inputs.
- Inspect dependency declarations for forbidden direction or leakage.
- Trace plugin discovery and failure paths.
- Check contract/schema changes against compatibility expectations.
- Cite file paths and line numbers for each finding.
Validation
Recommend:
./gradlew :core:extension:compileDebugKotlin :app:extension:compileDebugKotlin
Also compile any host app module touched by runtime changes. If unavailable, state compatibility risk.
Output
Return a concise Markdown report with:
- Scope and compatibility-sensitive APIs
- Pass/fail table for each audit check
- Evidence-backed findings with file paths
- Compatibility notes required in the PR
- Validation run or not run, with reason