Borrowing it
Nothing to install: this file belongs to RubenGlez/devicecloud-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.
curl -O https://raw.githubusercontent.com/RubenGlez/devicecloud-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/RubenGlez/devicecloud-mcpWrote 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.
[](https://agentmods.dev/instructions/rubenglez/devicecloud-mcp/agents-md)<a href="https://agentmods.dev/instructions/rubenglez/devicecloud-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/rubenglez/devicecloud-mcp/agents-md/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.
<a href="https://agentmods.dev/instructions/rubenglez/devicecloud-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/rubenglez/devicecloud-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01002 | $0.01002 |
| Opus 5.5 | $0.00401 | $0.00401 |
| Sonnet 5.5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
devicecloud-mcp 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
devicecloud-mcp
Triage failing DeviceCloud runs so your agent can fix them, without opening the dashboard.
The dashboard is no longer in your debug loop. When CI goes red, your agent pulls the failure straight into your editor (fail reasons, failure screenshots, logs, and flow history), finds the root cause, and you commit the fix. CI re-runs. You never open a browser tab.
Who it's for
Mobile teams running Maestro flows on DeviceCloud through CI, who debug failures with an AI coding agent (Claude Code, Cursor) instead of the web dashboard.
The problem
When a CI run fails, the only way to understand why lives in the DeviceCloud dashboard: open it, click into the run, read the fail reason, study the failure screenshot, cross-reference the logs, then switch back to your editor to fix the flow. The evidence you need to fix the test is stuck in a browser, away from the code and the agent that could act on it.
The promise
The MCP delivers the triage; your agent does the fix. One invocation turns a red run into root cause plus the exact artifacts to act on, your agent edits the flow or app code, and you commit. The dashboard stays closed.
Why it's different
- vs. the DeviceCloud dashboard: the dashboard shows a human why a run failed; this lets an agent read the same evidence and act on it: edit the flow, not just look at the screenshot.
- vs. the official DeviceCloud MCP: that ships a handful of thin endpoint wrappers built around running tests. This is triage-first: opinionated tools that hand the agent root cause and the right artifacts, not raw JSON to stitch together. Running isn't its job; CI owns that.
- vs. the Maestro MCP: that drives local devices to author and run tests. This is cloud-only and post-run: it works on the runs CI already executed.
Scope boundaries (deliberate)
- Doesn't trigger or re-run tests; CI plus
git commitowns that. - No
dcdCLI dependency; pure REST API,npx-and-go, read-only and safe (an agent can't burn credits). - Not a local-device or test-authoring tool.
- Cancelling a run is dashboard-only and outside the triage loop this is built for.
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.
- 2mo ago First seen · 62 lines · 1,002 tokens per session scan A 6e578b925ca9
devicecloud-mcp AGENTS.md is an instructions file published in the GitHub repository RubenGlez/devicecloud-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,002 tokens to every session, about $0.0040 per session on Opus 5.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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.