device-control

A plugin that provides an observe-then-act procedure for controlling an Android device through device interface and action tools.

In plain words
What is it for?
It supports interacting with apps and screens on a connected Android device.
Why use it?
It gives device-driving tasks a defined workflow for checking the screen before taking action.

Plugin 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.

Claude Code
/plugin marketplace add bearlike/Assistant
agentmods
npx agentmods add plugins/bearlike/assistant/device_control
Clone the repo
git clone --depth 1 https://github.com/bearlike/Assistant

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

device-control 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 yesterday.

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.

packages/mewbo_core/src/mewbo_core/builtin_plugins/device_control/.claude-plugin/plugin.json · 9 lines

What it actually says

{
  "name": "device-control",
  "display_name": "Device Control",
  "description": "Observe→act playbook for driving an Android device through the device_ui / device_action tools.",
  "version": "0.1.0",
  "author": "Mewbo",
  "requires-capabilities": ["device_control"]
}
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. yesterday First seen · 9 lines scan A cea6da8eddb6

Subscribe to this mod's changes

device-control is a plugin published in the GitHub repository bearlike/Assistant (41 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.