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 rules/sandraschi/yahboom-mcp/cursorrulesgit clone --depth 1 https://github.com/sandraschi/yahboom-mcpWhat 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.00150 | $0.00150 |
| Opus 5 | $0.00075 | $0.00075 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
cursorrules 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 2d 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
yahboom-mcp — Cursor Rules
Robot control server. Do not move the physical robot without checking health first.
Session Context (Yahboom MCP)
MCP server for the Yahboom Raspbot v2 (Boomy) ROS 2 robot: motion, sensors, LIDAR, camera PTZ, voice, display, lightstrip, missions, and diagnostics.
Before starting work:
- Check robot health:
yahboom_tool(operation="health_check") - List live ROS topics:
ros_topic_list()
At end of work:
- Stop the robot if you moved it:
yahboom_tool(operation="stop") - Confirm server state via
query_logs(limit=20)
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.
- 2d ago First seen · 16 lines · 150 tokens per session scan A 38c6c89dd075
cursorrules is a cursor rule published in the GitHub repository sandraschi/yahboom-mcp (4 stars, last pushed 4d ago), licensed MIT. It adds 150 tokens to every session, about $0.0007 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-31.
Other cursor rules, from other repositories
cursorrules
You have access to robotics orchestration: virtual robot control, ROS 2 bridge, Unity/VRChat integration, robot CRUD, and OSC control.
cursorrules
You have access to Dreame robot vacuum control via DreameHome cloud: device status, LIDAR map, and cleaning controls.
cursorrules
See CLAUDE.md for full context. Quick rules.
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.
cli-error-handling
CLI command error handling patterns.