agentleFS
Rudra-raviRudra-ravi/frida-skills/frida-script-review/SKILL.md

frida-script-review

Skill3 starsChanged 6 months agoMITView on GitHub

Review, harden, and simplify Frida scripts before running CodeShare snippets, universal bypasses, broad hooks, native pointer code, Java hooks, or ObjC hooks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

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 running public, generated, or mutation-heavy Frida scripts.

    line 8
  2. Distinctive:

    Check timing: spawn vs attach, module load, class loader, ObjC availability.

    line 14
  3. Very specific:

    Check safety: null pointers, overloads, string lifetimes, retval copies, recursion, noisy hooks.

    line 15

≈ “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 Script Review

Use this skill before running public, generated, or mutation-heavy Frida scripts.

Review Pass

  1. Identify platform assumptions: Android, iOS, native, desktop, Gadget.
  2. Identify mutation points: return replacement, argument rewrite, file writes, process control, network changes.
  3. Check timing: spawn vs attach, module load, class loader, ObjC availability.
  4. Check safety: null pointers, overloads, string lifetimes, retval copies, recursion, noisy hooks.
  5. Reduce broad bundles to the hooks relevant to the target behavior.

Red Flags

  • Blind universal bypass without proof of which hook fired.
  • Native pointer reads without null or length checks.
  • String replacement into fixed buffers without proving buffer size.
  • Java method hook without explicit overload where overloads exist.
  • ObjC selector assumed without checking ObjC.available and class/method presence.
  • retval or argument wrappers stored for later use instead of copied.
  • Logs that print secrets unnecessarily.

Hardening Pattern

Before mutation:

console.log("hook fired", targetName);
console.log(Thread.backtrace(this.context, Backtracer.ACCURATE)
  .map(DebugSymbol.fromAddress).join("\n"));

After proof:

if (shouldPatchThisCall()) {
  retval.replace(1);
}

Output

Return:

  • Risk summary.
  • Exact lines or hook blocks to keep, remove, or change.
  • Safer reviewed script or patch.
  • Verification command and expected proof.

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.