agentleFS
Sign inStart free
Rudra-raviRudra-ravi/frida-skills/frida-agent-builder/SKILL.md

frida-agent-builder

Skill3 starsChanged 6 months agoMITView on GitHub

Build maintainable Frida agent projects with TypeScript, frida-compile, RPC exports, helpers, logging, version checks, and multi-hook organization.

  • Installs packages

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for reusable Frida agents and multi-script projects.

    line 8
  2. Distinctive:

    Prefer a small TypeScript agent when scripts will grow beyond a single hook:

    line 12
  3. Distinctive:

    Keep one hook family per file.

    line 29
  4. Distinctive:

    Use structured logging with tags and JSON for complex values.

    line 31
  5. Very specific:

    Add rpc.exports only for host-controlled actions or test probes.

    line 32
  6. Distinctive:

    Avoid global broad hooks unless the task explicitly requires discovery.

    line 33
  7. Distinctive:

    Keep generated artifacts out of source control unless the repository convention includes them.

    line 34
  8. Very specific:

    Use scripts/scaffold-frida-agent.py to create a minimal TypeScript Frida agent:

    line 38
  9. Very specific:

    Read references/agent-patterns.md for project conventions, RPC patterns, host command examples, and packaging notes.

    line 53

≈ “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 Agent Builder

Use this skill for reusable Frida agents and multi-script projects.

Project Shape

Prefer a small TypeScript agent when scripts will grow beyond a single hook:

agent/
├── package.json
├── tsconfig.json
├── src/
│   ├── index.ts
│   ├── log.ts
│   └── hooks/
└── dist/

For Frida 17 and Java APIs in bundled agents, include frida-java-bridge when required by the build/runtime style.

Build Rules

  • Keep one hook family per file.
  • Export an init() function per hook family and call it from src/index.ts.
  • Use structured logging with tags and JSON for complex values.
  • Add rpc.exports only for host-controlled actions or test probes.
  • Avoid global broad hooks unless the task explicitly requires discovery.
  • Keep generated artifacts out of source control unless the repository convention includes them.

Scaffold Script

Use scripts/scaffold-frida-agent.py to create a minimal TypeScript Frida agent:

python3 /path/to/frida-agent-builder/scripts/scaffold-frida-agent.py ./agent --java

Then install and build:

npm install
npm run build

References

Read references/agent-patterns.md for project conventions, RPC patterns, host command examples, and packaging notes.

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.

Check your setup, free