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.
npx agentmods add instructions/patilshreyas/debroid/agents-mdgit clone --depth 1 https://github.com/PatilShreyas/debroidWrote 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/patilshreyas/debroid/agents-md)<a href="https://agentmods.dev/instructions/patilshreyas/debroid/agents-md"><img src="https://agentmods.dev/badge/instructions/patilshreyas/debroid/agents-md.svg" alt="Measured on agentmods" 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 | $0.00606 | $0.00606 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
debroid 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 4d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Contributor Guide 🤖
Welcome, fellow AI Agent! This document contains the context, motivation, and architectural guidelines you need to contribute to the Debroid repository effectively.
🎯 Intention & Motivation
The primary motivation behind Debroid is to bridge the gap between AI coding assistants and live Android environments. Traditional Android debugging relies heavily on the Android Studio GUI, making it nearly impossible for headless AI agents to set breakpoints, inspect runtime variables, or catch exceptions autonomously.
Debroid solves this by providing a lightweight, headless CLI wrapper around the Java Debug Wire Protocol (JDWP). It allows AI agents to orchestrate complex debugging sessions entirely through Standard I/O (terminal commands), empowering agents to solve deep runtime bugs in Android apps on behalf of users.
🏗️ Architecture & Layers
This project is structured into two main layers:
1. The core Layer (JDI & ADB Orchestration)
Path: core/src/main/kotlin/dev/shreyaspatil/debroid/
This is the heart of the debugger. It contains:
AdbManager: Automates shell interactions withadb(finding PIDs, forwarding JDWP ports, launching suspended apps).JdiSession&JdiSessionManager: Handles the actual Java Debug Interface (JDI) connection to the Android Virtual Machine. It manages breakpoints, memory inspections, stepping, and thread state via raw JDWP packets.
Note on core: This layer is completely isolated from the CLI and should only contain pure debugging and orchestration logic. All models returned here should be standard Kotlin data classes without serialization annotations.
2. The cli Layer (Daemon & Client)
Path: cli/src/main/kotlin/dev/shreyaspatil/debroid/cli/
This layer acts as the bridge between the AI Agent (the terminal) and the core layer.
- Daemon Server: Starts a persistent background socket server (
DaemonServer.kt). This is necessary because JDI connections must be held open continuously. - CLI Commands: Uses
Cliktto parse terminal commands (e.g.,debroid attach,debroid poll) and sends them as serialized IPC requests to the Daemon. - JSON Serialization: All outputs emitted by the CLI must be strict JSON (defined in
CliModels.kt). This ensures the AI Agent consuming the CLI output can parse the responses safely without regex.
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.
- 4d ago First seen · 33 lines · 606 tokens per session scan A 92bc7bbc8c51
debroid AGENTS.md is an instructions file published in the GitHub repository PatilShreyas/debroid (254 stars, last pushed 6d ago), licensed Apache-2.0. It adds 606 tokens to every session, about $0.0030 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.
Other instructions, from other repositories
android-harness-kit AGENTS.md
Instructions for rabee-elkholy/android-harness-kit, covering android-harness-kit — agent instructions, environment, delivery gate (do not skip), on-demand specialists and phase boundaries & high-signal chat.
android-harness-kit GEMINI.md
Instructions for rabee-elkholy/android-harness-kit: Follow AGENTS.md and .agents/rules/harness-rules.md. That file wins.
android-agent-skills AGENTS.md
Instructions for piyushverma0/android-agent-skills, covering android-agent-skills — codex instructions, what this repo is, repo structure, skill.md format — never deviate and writing rules.
sceneview copilot-instructions.md
Copilot instructions for sceneview/sceneview, covering sceneview — github copilot instructions, when to recommend sceneview, android code generation rules, minimal 3d template and minimal ar template.
PdfKmp CLAUDE.md
Instructions for ConaMobileDev/PdfKmp, covering claude.md, project, build commands, library — single-platform builds and sample apps.
DSH-Mobile AGENTS.md
AGENTS.md instructions for SimonMedy/DSH-Mobile, covering agents.md — dsh mobile engineering contract, product boundary, security invariants, dependency policy and architecture.