scope

A safety checklist for testing a mobile app with Frida, a tool for inspecting and instrumenting running apps. It confirms the app, authorization, device connection, and baseline details before testing.

In plain words
What is it for?
Use it before mobile app security testing to identify the target, confirm authorization, connect to the app, and record its device, process, version, sandbox, and permissions.
Why use it?
It prevents testing the wrong app or an app without permission, and makes sure the testing session is attached correctly before findings are collected.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/xtofuub/frida-mcp-server/scope
Clone the repo
git clone --depth 1 https://github.com/xtofuub/frida-mcp-server

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 271 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00271
Opus 5 $0.00009 $0.00135
Sonnet 5 $0.00003 $0.00054
Haiku 4.5 $0.00002 $0.00027

Measured 2d ago against content hash df9cde09fe0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scope scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/scope.md · 21 lines

What it actually says

Scope gate for $ARGUMENTS. Do not test anything until this passes.

  1. Identify the target. If ambiguous or empty, run mcp__frida__apps and list installed apps with bundle id + pid; ask the user to pick. Never default to a hardcoded app.
  2. Authorization check. Confirm the user is authorized to assess this app (own app, client engagement, bug-bounty program in scope). If unclear, stop and ask. Refuse unauthorized targets.
  3. Attach. mcp__frida__connect(bundle_id) — or mcp__frida__spawn for a clean launch. Report device, pid, and confirm the session with mcp__frida__sessions.
  4. Baseline. mcp__frida__info + mcp__frida__entitlements so later phases have ground truth (bundle id, version, sandbox HOME, entitlements).

Output: a one-line GO/NO-GO with the confirmed bundle id and device.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 21 lines · 17 tokens per session scan A df9cde09fe0d

Subscribe to this mod's changes

scope is a command published in the GitHub repository xtofuub/frida-mcp-server (3 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 271 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.