agentleFS
Rudra-raviRudra-ravi/frida-skills/frida-codeshare-search/SKILL.md

frida-codeshare-search

Skill3 starsChanged 6 months agoMITView on GitHub

Search Frida CodeShare with curl, extract project metadata and script source, review snippets, and turn scripts into local agents or commands.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when a user wants to find, inspect, download, adapt, or run Frida CodeShare scripts.

    line 8
  2. Distinctive:

    Treat CodeShare scripts as reconnaissance first.

    line 13
  3. Very specific:

    Prefer local review with -l script.js after extraction.

    line 14
  4. Distinctive:

    Verify the script matches the target platform, app version, library names, symbols, and Frida version before changing behavior.

    line 15
  5. Distinctive:

    Run a reviewed local script:

    line 55
  6. Distinctive:

    Run directly through CodeShare when direct execution is acceptable:

    line 61
  7. Very specific:

    If the CodeShare page shows a placeholder like ${projectSlug}, use the slug from the project URL.

    line 67

≈ “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 CodeShare Search

Use this skill when a user wants to find, inspect, download, adapt, or run Frida CodeShare scripts.

Rules

  • Confirm authorization and target scope before running third-party instrumentation.
  • Treat CodeShare scripts as reconnaissance first. Read the source before running it.
  • Prefer local review with -l script.js after extraction; use frida --codeshare only when the user accepts fetching and running public code directly.
  • Verify the script matches the target platform, app version, library names, symbols, and Frida version before changing behavior.

Search With Curl

Fetch the search page with URL-encoded query parameters:

curl -fsSL --get --data-urlencode "query=instagram" "https://codeshare.frida.re/search/" -o codeshare-search.html

Parse the result cards:

python3 /path/to/frida-codeshare-search/scripts/codeshare_extract.py search codeshare-search.html

The parser reports title, author, URL, likes, views, and description. Pick candidates by platform fit, recency/version in title, specific framework coverage, and enough source clarity to audit.

Extract A Project Script

Fetch the project page:

curl -fsSL "https://codeshare.frida.re/@Eltion/instagram-ssl-pinning-bypass/" -o codeshare-project.html

Extract the embedded projectSource into a local script:

python3 /path/to/frida-codeshare-search/scripts/codeshare_extract.py project codeshare-project.html -o agent.js

Then inspect before execution:

sed -n '1,220p' agent.js

Run Options

Run a reviewed local script:

frida -U -f com.instagram.android -l agent.js --no-pause

Run directly through CodeShare when direct execution is acceptable:

frida -U --codeshare Eltion/instagram-ssl-pinning-bypass -f com.instagram.android --no-pause

If the CodeShare page shows a placeholder like ${projectSlug}, use the slug from the project URL.

Adaptation Checklist

  • Android Java hooks are inside Java.perform() and overloads are explicit.
  • Native hooks wait for the module before resolving exports or symbols.
  • iOS hooks check ObjC.available and confirm class/selectors or symbols exist.
  • Broad SSL/root/integrity bypass bundles are reduced to the hooks that actually fire.
  • Logs prove which hook changed behavior; failures include the exact command, app version, Frida version, and target architecture.

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.