agentleFS
Rudra-raviRudra-ravi/frida-skills/frida-setup-checklist/SKILL.md

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

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
  1. Distinctive:

    Use this skill before writing hooks or when the environment is unknown.

    line 8
  2. Very specific:

    If frida is missing, install user-local tools unless the project documents another path:

    line 19
  3. Distinctive:

    Use a smoke script before loading real hooks:

    line 46

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 -Uai

If frida is missing, install user-local tools unless the project documents another path:

python3 -m pip install --user --upgrade frida-tools

Android 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 -Uai

Match 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-pause

Use 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.