Rudra-ravi/frida-skills / frida-agent-builder
frida-agent-builder
VerifiedBuild maintainable Frida agent projects with TypeScript, frida-compile, RPC exports, helpers, logging, version checks, and multi-hook organization.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.5 KB |
| agents/openai.yaml | config | 192 B |
| references/agent-patterns.md | markdown | 763 B |
| scripts/scaffold-frida-agent.pyexecutable | script | 2.0 KB |
SKILL.md
View on GitHub---
name: frida-agent-builder
description: Build maintainable Frida agent projects with TypeScript, frida-compile, RPC exports, helpers, logging, version checks, and multi-hook organization.
---
# 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:
```text
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:
```bash
python3 /path/to/frida-agent-builder/scripts/scaffold-frida-agent.py ./agent --java
```
Then install and build:
```bash
npm install
npm run build
```
## References
Read `references/agent-patterns.md` for project conventions, RPC patterns, host command examples, and packaging notes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |