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.
git clone --depth 1 https://github.com/hyperb1iss/droidmindWrote 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/rules/hyperb1iss/droidmind/003_cursor_docs)<a href="https://agentmods.dev/rules/hyperb1iss/droidmind/003_cursor_docs"><img src="https://agentmods.dev/badge/rules/hyperb1iss/droidmind/003_cursor_docs/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/rules/hyperb1iss/droidmind/003_cursor_docs"><img src="https://agentmods.dev/badge/rules/hyperb1iss/droidmind/003_cursor_docs.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.00000 | $0.00245 |
| Opus 5.5 | $0.00000 | $0.00098 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
003_cursor_docs 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 1mo 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.
What it actually says
Documentation Organization
Project Overview
- @project.md: Main architectural documentation
- @README.md: Quick-start guide and feature summary
- @plan.md: Development roadmap and planning
Technical References
- @python-mcp.md: Guide for Model Context Protocol Python implementation
- @mcp-src.txt: Source reference for MCP implementation
- @llms-full.txt: LLM integration documentation
Examples and Testing
- @examples.txt: Example usage scenarios and code snippets
- @test_examples.py: Python test examples for MCP integrations
- @doc-summary.txt: Condensed documentation for quick reference
Documentation Guidelines
- Follow consistent formatting across all docs
- Include code examples for all key features
- Cross-reference between docs using @ notation
- Update documentation when implementations change
- Include version compatibility information
Key Concepts to Document
- Device connection and management
- ADB command execution and security
- MCP resource and tool implementations
- Client integration patterns
- Security best practices
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.
- 1mo ago First seen · 35 lines · 245 tokens per session scan A 7c9051718acd
003_cursor_docs is a cursor rule published in the GitHub repository hyperb1iss/droidmind (439 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 245 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.