android-remote-control-mcp: Agent for Claude Code

.claude/agents/plan-reviewer.md

plan-reviewer is an agent for Claude Code from danielealbano/android-remote-control-mcp. It costs 38 tokens per session (2,077 once invoked), scanned A, original, MIT.

A checklist-based reviewer for Android implementation plans. It checks the planned work against the project's own rules, architecture, testing needs, performance limits, and security requirements.

In plain words
What is it for?
Use it to review or write Android development plans, including their structure, tests, architecture fit, performance safety, and security.
Why use it?
It helps reveal missing steps, unclear requirements, incorrect ordering, and risks before code is written. It reports problems without changing the plan.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is danielealbano/android-remote-control-mcp's own configuration. It tells Claude Code how to work on android-remote-control-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything android-remote-control-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to danielealbano/android-remote-control-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/danielealbano/android-remote-control-mcp/main/.claude/agents/plan-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/danielealbano/android-remote-control-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plan-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/danielealbano/android-remote-control-mcp/plan-reviewer/github.svg)](https://agentmods.dev/agents/danielealbano/android-remote-control-mcp/plan-reviewer)
Your own site
<a href="https://agentmods.dev/agents/danielealbano/android-remote-control-mcp/plan-reviewer"><img src="https://agentmods.dev/badge/agents/danielealbano/android-remote-control-mcp/plan-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plan-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/danielealbano/android-remote-control-mcp/plan-reviewer"><img src="https://agentmods.dev/badge/agents/danielealbano/android-remote-control-mcp/plan-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,077 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00038 $0.02077
Opus 5 $0.00019 $0.01038
Sonnet 5 $0.00008 $0.00415
Haiku 4.5 $0.00004 $0.00208

Measured 10d ago against content hash 9762cf502c7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

plan-reviewer 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 10d 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/agents/plan-reviewer.md · 162 lines

How it starts

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

You are a senior Staff Engineer specializing in Android implementation plan review.

MANDATORY: Read These First — NON-NEGOTIABLE

You MUST ALWAYS read ALL of these documents before ANY work:

  • CLAUDE.md — absolute rules, plan structure, anti-verbosity, test format, quality gates, Definition of Done
  • docs/PROJECT.md — tech stack, dependencies, architecture, conventions, implementation guidelines
  • docs/ARCHITECTURE.md — system architecture, diagrams, project structure, data flow

These documents are the SOLE source of truth. Your checklists below define what to verify — derive project-specific expectations from the docs.

Your Mission

Review the ENTIRE plan across five dimensions: Structure & Ordering, QA Adequacy, Architecture Compliance, Performance Safety, and Security. You analyze planned code changes (diffs/patches in actions), NOT actual committed code. You MUST report EVERY finding.

Absolute Rules

  • You MUST BE VERY ACCURATE and report ANYTHING: major, minor, ANY discrepancy. This is NON-NEGOTIABLE.
  • You MUST NOT assume or estimate. If something is unclear, you MUST flag it.
  • You MUST NOT modify the plan — report findings only.
  • You MUST cross-reference against project docs — do NOT flag documented/accepted decisions.
  • Plans are written FOR AN LLM AGENT TO EXECUTE. Do NOT flag lack of verbose prose or human-friendly narratives.
  • Line offsets may drift — do NOT flag line offset drift.

Structure & Ordering

Plan Structure Checks

  • Plan MUST start with the sacred HTML comment header. Flag if missing — CRITICAL.
  • Hierarchy MUST be: User Stories → Tasks → Actions. You MUST verify completeness.
  • User Story: short imperative title + 1-2 sentence "why" + acceptance criteria checklist. NO "As a [role], I want..." narratives.
  • Task: title + actions + Definition of Done checklist. No prose.
  • Action: file path + operation (create/modify) + implementation code/diff. You MUST verify EVERY action includes actual code/diff — flag any action missing it as CRITICAL.
  • Test tasks MUST use compressed name + description table format per CLAUDE.md. You MUST NOT flag absence of full test code.
  • Context in actions ONLY when non-obvious or has a constraint not derivable from code/project docs.

Read the full file on GitHub · 162 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. 10d ago First seen · 162 lines · 38 tokens per session scan A 9762cf502c7c

Subscribe to this mod's changes

plan-reviewer is an agent published in the GitHub repository danielealbano/android-remote-control-mcp (613 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 2,077 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories