frida-setup-checklist
Skill3 starsChanged 6 months agoMITView on GitHub
Prepare and verify a Frida environment, including host tools, Android frida-server, iOS setup, USB or remote transport, version matching, and smoke tests.
- Installs packages
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- frida-agent-builderSkill
- frida-android-hooksSkill
- frida-anti-instrumentationSkill
- frida-codeshare-searchSkill
- frida-data-extractionSkill
- frida-gadget-injectionSkill
- frida-ios-hooksSkill
- frida-native-hooksSkill
- frida-script-reviewSkill
- frida-tls-pinningSkill
- frida-tools-referenceSkill
- frida-tracing-discoverySkill
- frida-troubleshootingSkill
- frida-workflowSkill
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
- Distinctive: line 8
Use this skill before writing hooks or when the environment is unknown.
- Very specific: line 19
If frida is missing, install user-local tools unless the project documents another path:
- Distinctive: line 46
Use a smoke script before loading real hooks:
≈ “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
Frida Setup Checklist
Use this skill before writing hooks or when the environment is unknown.
Host Checks
python3 -m pip show frida frida-tools
frida --version
frida-ls-devices
frida-ps -UaiIf frida is missing, install user-local tools unless the project documents another path:
python3 -m pip install --user --upgrade frida-toolsAndroid Checks
adb devices
adb shell getprop ro.product.cpu.abi
adb shell getprop ro.build.version.release
adb shell id
adb shell /data/local/tmp/frida-server --version
frida-ps -UaiMatch host frida --version to the device frida-server major/minor version. If versions differ, fix that before debugging hooks.
iOS Checks
frida-ls-devices
frida-ps -Uai
frida -U -f com.example.app -l smoke.js --no-pauseUse a smoke script before loading real hooks:
console.log("platform", Process.platform, "arch", Process.arch);
console.log("ObjC.available", ObjC.available);Minimal Smoke Scripts
Android:
console.log("platform", Process.platform, "arch", Process.arch);
console.log("Java.available", Java.available);
Java.perform(() => console.log("Java.perform ok"));Native-only target:
console.log(Process.id, Process.arch, Process.pointerSize);
for (const m of Process.enumerateModules().slice(0, 10)) {
console.log(m.name, m.base, m.size);
}Proof To Report
- Exact host Frida version and remote server/Gadget version.
- Device, OS version, architecture, package/bundle/process id.
- Attach or spawn command used.
- Smoke script output proving
Java,ObjC, or native module access.
References
- Official Frida installation docs: https://frida.re/docs/installation/
- Official Android docs: https://frida.re/docs/android/
- Official iOS docs: https://frida.re/docs/ios/
- OWASP MASTG Frida Android: https://mas.owasp.org/MASTG/tools/android/MASTG-TOOL-0001/
- OWASP MASTG Frida iOS: https://mas.owasp.org/MASTG/tools/ios/MASTG-TOOL-0039/
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.

