mobile-debug-tools AGENTS.md

An AGENTS.md instruction file for a TypeScript server that helps debug Android and iOS mobile apps. It points agents to the main code areas and the repository's build and test commands.

In plain words
What is it for?
Use it when working on mobile-debug-mcp, especially for interaction tools, screenshots and logs, app management, system checks, builds, or tests.
Why use it?
It gives a coding agent the project context and checks it should follow, reducing guesses about where code belongs or how to validate changes.

Instructions file for CodexOpenCode

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 instructions/clivejefferies/mobile-debug-tools/agents-md
Clone the repo
git clone --depth 1 https://github.com/clivejefferies/mobile-debug-tools

Made for: Codex, OpenCode.

Per session 898 This file is loaded in full into every session.
When invoked 898 The same file — it is already loaded in full.
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.00898 $0.00898
Opus 5 $0.00449 $0.00449
Sonnet 5 $0.00180 $0.00180
Haiku 4.5 $0.00090 $0.00090

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

Security

Grade A, and why

mobile-debug-tools AGENTS.md 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.

AGENTS.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This file is the cold-start entrypoint for autonomous agents that arrive in this public repository without prior context.

It is intentionally vendor-neutral and should be useful to Copilot, Codex, Claude, or custom agent systems.

What this repository is

mobile-debug-mcp is an MCP server for mobile app debugging on Android and iOS. The codebase is TypeScript and the built server entrypoint is dist/server.js.

Primary areas:

  • src/server.ts — runtime entrypoint
  • src/server-core.ts — tool registration and dispatch logic
  • src/interact/ — tap, swipe, typing, waits, and interaction helpers
  • src/observe/ — logs, screenshots, UI tree, fingerprints, snapshots
  • src/manage/ — build, install, start, terminate, restart, reset-app-data
  • src/system/ — environment and toolchain health checks
  • src/utils/ — shared helpers and platform-specific utility code

First things an agent should know

  1. Prefer existing helpers and conventions over introducing new frameworks or abstractions.
  2. The repository already has a test structure; place tests in the correct tree instead of inventing new ones.
  3. Use existing validation commands:
    • npm run build
    • npm run lint
    • npm run test:unit
    • npm run test:device
  4. Device tests are split intentionally:
    • test/device/automated/... = automated smoke/integration coverage
    • test/device/manual/... = helper/debug/manual scripts
  5. Unit tests use the current lightweight self-running tsx pattern rather than a dedicated framework.

Where to look for deeper guidance

Skills

Portable agent skills live under skills/.

  • skills/README.md — repo-wide skill convention
  • skills/mcp-builder/ — build/install/toolchain guidance
  • skills/test-authoring/ — test creation and placement guidance
  • skills/rfc-review/ — RFC review rubric and response template

If the task is about creating or updating tests, load skills/test-authoring/SKILL.md first.

If the task is about building, installing, or diagnosing native tooling, load skills/mcp-builder/SKILL.md first.

Read the full file on GitHub · 91 lines

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 · 91 lines · 898 tokens per session scan A 28ba0bcc166f

Subscribe to this mod's changes

mobile-debug-tools AGENTS.md is an instructions file published in the GitHub repository clivejefferies/mobile-debug-tools (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 898 tokens to every session, about $0.0045 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.