agentleFS
Rudra-raviRudra-ravi/frida-skills/frida-data-extraction/SKILL.md

frida-data-extraction

Skill3 starsChanged 6 months agoMITView on GitHub

Use Frida to observe and extract runtime data such as HTTP, headers, tokens, JSON, crypto values, preferences, SQLite, files, memory, and byte arrays.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the goal is to observe runtime data rather than bypass a check.

    line 8
  2. Distinctive:

    Only extract data from systems the user is authorized to test.

    line 12
  3. Distinctive:

    Avoid printing secrets into shared logs unless the user explicitly needs them.

    line 13
  4. Distinctive:

    Prefer structured logs with redaction for tokens, cookies, passwords, and private keys.

    line 14
  5. Distinctive:

    Use both hex and text only when the data is valid text.

    line 45

≈ “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 Data Extraction

Use this skill when the goal is to observe runtime data rather than bypass a check.

Rules

  • Only extract data from systems the user is authorized to test.
  • Avoid printing secrets into shared logs unless the user explicitly needs them.
  • Prefer structured logs with redaction for tokens, cookies, passwords, and private keys.
  • Copy pointer and retval data inside callbacks; Frida may recycle callback objects.

Android Boundaries

Java.perform(() => {
  const Base64 = Java.use("android.util.Base64");
  Base64.encodeToString.overload("[B", "int").implementation = function (bytes, flags) {
    const out = this.encodeToString(bytes, flags);
    console.log("Base64.encodeToString ->", out);
    return out;
  };
});

High-signal targets: request builders, JSON serializers, SharedPreferences, SQLite APIs, keystore wrappers, crypto APIs, WebView bridges, file I/O.

iOS Boundaries

High-signal targets: NSURLRequest, NSURLSession, NSJSONSerialization, Keychain wrappers, NSUserDefaults, SQLite, CommonCrypto, file APIs, pasteboard.

Native Buffers

function dump(ptr, len) {
  if (ptr.isNull() || len <= 0) return;
  console.log(hexdump(ptr, { length: Math.min(len, 256), ansi: false }));
}

Use both hex and text only when the data is valid text. Binary crypto material often is not.

Verification

  • Logs are tied to a user action or request.
  • The source and encoding of each value is clear.
  • Sensitive values are redacted unless needed.
  • The hook does not change the target behavior unless explicitly requested.

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.