MCPInstall

frida-mcp-workflow

by yfe404AI & Agents

Enforce safe Frida 17 MCP operations with strict phase gating. Use when attaching/spawning sessions, writing or loading scripts, applying Java/native hooks, troubleshooting instrumentation failures, or interpreting Frida MCP output. Require docs-first usage and run the mandatory workflow: Idea - Scripting - Execution - Notes.

Installs
74
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/yfe404/frida-mcp-skills --skill frida-mcp-workflow
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads frida-mcp-workflow automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Frida MCP Workflow

Run these phases in order. Do not skip phases.

Phase 1: Idea

  • Define target: process/app identifier, platform, and session type.
  • Define objective: what signal/result must be observed.
  • Query docs before function use: call search_frida_docs for each non-trivial API/runtime assumption.
  • Record 2-5 Doc facts used bullets before scripting.
  • Assume Frida 17 semantics only. Do not use Frida 16 assumptions.

Hard stop:

  • If docs are missing or ambiguous, narrow the query and retry before scripting.

Phase 2: Scripting

  • Prefer saved files over inline scripts.
  • Allow inline only for short, read-only probes.
  • For hook scripts, require file-based scripts and load_script.
  • Declare script_id, purpose, and explicit target list (module/symbol or class/method).
  • Add idempotence guard to prevent duplicate install.
  • Define teardown path (uninstall RPC export or equivalent).

Script policy:

  • If script is more than 25 lines or writes hooks, save it to a file.
  • If modifying existing behavior, include rollback logic in the script.

Phase 3: Execution

  • Preflight checks before load/execute:
    • session exists and is alive
    • loaded scripts are listed
    • target overlap is checked
  • If overlap exists, unload/replace old script before loading new one.
  • Do not attach multiple scripts to the same target unless explicitly intentional.
  • Prefer one script per purpose (probe, hook, tracer).

Failure handling:

  • On Java is not defined, stop retries and re-check docs/runtime assumptions.
  • On attach/spawn failures, run diagnostics before retrying instrumentation.
  • On oversized docs output, reduce query scope or paginate; do not guess.

Phase 4: Notes

  • Persist notes to file after each execution cycle.
  • Record:
    • doc facts used
    • script ledger (loaded/unloaded/current active)
    • observed output and verification status
    • errors and root cause
    • cleanup status and next action
  • Confirm teardown is complete when ending work.

Required Response Shape

For each task, output four sections in this order:

  1. Idea
  2. Scripting
  3. Execution
  4. Notes

Do not run tool calls in Execution before Idea and Scripting are present.

FAQ

What does the frida-mcp-workflow skill do?

Enforce safe Frida 17 MCP operations with strict phase gating. Use when attaching/spawning sessions, writing or loading scripts, applying Java/native hooks, troubleshooting instrumentation failures, or interpreting Frida MCP output. Require docs-first usage and run the mandatory workflow: Idea - Scripting - Execution - Notes.

How do I install frida-mcp-workflow?

Run npx skills add https://github.com/yfe404/frida-mcp-skills --skill frida-mcp-workflow in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/frida-mcp-workflow/ (personal) or .claude/skills/frida-mcp-workflow/ (project).

Which AI agents can use frida-mcp-workflow?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is frida-mcp-workflow safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains frida-mcp-workflow?

It is published by yfe404 in yfe404/frida-mcp-skills. It has 74 recorded installs.

Popular ai & agents skills

View category →

google-agents-cli-publish

google/agents-cli

This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).

AI & Agents513.9K installs

google-agents-cli-eval

google/agents-cli

This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).

AI & Agents513.5K installs

skill-creator

anthropics/skills

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

OfficialAI & Agents416.4K installs

codex-pet

prime-skills/runcomfy-agent-skills

Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.

AI & Agents402.1K installs

full-output-enforcement

leonxlnx/taste-skill

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

AI & Agents401K installs

executing-plans

obra/superpowers

Use 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

AI & Agents245.7K installs