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/sidkandan/universal-remote-control/gemini-mdgit clone --depth 1 https://github.com/sidkandan/universal-remote-controlWrote 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/sidkandan/universal-remote-control/gemini-md)<a href="https://agentmods.dev/instructions/sidkandan/universal-remote-control/gemini-md"><img src="https://agentmods.dev/badge/instructions/sidkandan/universal-remote-control/gemini-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.03182 | $0.03182 |
| Opus 5 | $0.01591 | $0.01591 |
| Sonnet 5 | $0.00636 | $0.00636 |
| Haiku 4.5 | $0.00318 | $0.00318 |
Grade C, and why
universal-remote-control GEMINI.md scanned grade C with 1 finding 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 3d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- This file contains instructions for Gemini CLI agents. For human documentation, see README.md --> How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
URC — CLI-to-CLI Communication & RC Bridge
What This Is
URC enables cross-CLI communication between Claude Code, Codex, and Gemini panes via MCP tools backed by a shared SQLite coordination database.
RC Bridge
The RC Bridge makes this Gemini pane controllable from the Claude Code phone app. A Haiku relay pane forwards messages between the phone app and this pane.
How it works:
- A Claude Code relay pane runs the
rc-bridgeagent (Haiku model) - It's pre-configured with target pane ID and CLI type via tmux pane options (set by
urc-spawn.sh) - State is stored in tmux pane options (
@bridge_target,@bridge_cli,@bridge_relays) - Phone message -> relay hook dispatches to this pane via
send.sh-> your response is captured byhook.shand written to a push file -> relay picks it up on next wake and displays it verbatim on phone
Launch: Use /rc command in this Gemini pane, or /rc-bridge gemini from Claude Code.
Available MCP Tools (urc_coordination — 11 tools)
Note: Gemini CLI uses underscores in MCP server names (
urc_coordination) instead of hyphens (urc-coordination) — this is a Gemini CLI naming convention requirement. The naming is transparent: just usemcp__urc_coordination__tool_name()syntax. The MCP server isurc/core/server.py.
NEVER run python3 urc/core/server.py as a shell command — it is an MCP server, not a CLI tool.
| Tool | Purpose |
|---|---|
register_agent |
Register this pane in the coordination DB |
heartbeat |
Send a heartbeat with context usage |
get_fleet_status |
List all registered agents |
rename_agent |
Set a display label for a pane |
dispatch_to_pane |
Send a message to a tmux pane via send.sh |
read_pane_output |
Capture recent output from a pane's buffer |
send_message |
Send a message to another agent (use notify=true to include wake nudge) |
receive_messages |
Get unread messages |
kill_pane |
Kill a tmux pane (requires explicit confirmation) |
cancel_dispatch |
SIGINT target + clear signals + unblock waiting dispatcher |
bootstrap_validate |
Validate CWD/directories/hook/tmux setup |
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.
- 3d ago First seen · 177 lines · 3,182 tokens per session scan C eacfd46d4d20
universal-remote-control GEMINI.md is an instructions file published in the GitHub repository sidkandan/universal-remote-control (13 stars, last pushed 5mo ago), licensed MIT. It adds 3,182 tokens to every session, about $0.0159 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
guild AGENTS.md
Instructions for mathomhaus/guild, covering guild — agent bootstrap, first action — bootstrap guild mcp, repo facts, tool discipline and when onboarding.
untether GEMINI.md
Instructions for littlebearapps/untether, covering untether — gemini instructions, stack & conventions, architecture, key rules and testing.
nelson CLAUDE.md
Instructions for Aspegio/nelson, covering nelson, key references, maintainability sensors, active sensors and suppressing or bumping a sensor.
claude-tui CLAUDE.md
Instructions for slima4/claude-tui, covering claude.md, project overview, top-level scripts, tools and claude-code-statusline.
claude-tui AGENTS.md
Instructions for slima4/claude-tui, covering agents.md, quick commands, testing, gotchas (hard-won knowledge) and local development.
gnap CLAUDE.md
Instructions for farol-team/gnap, covering claude.md, what this repo is, architecture, key files and core protocol concepts.