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/voidxela/roku-dev-mcp/agents-mdgit clone --depth 1 https://github.com/voidxela/roku-dev-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/voidxela/roku-dev-mcp/agents-md)<a href="https://agentmods.dev/instructions/voidxela/roku-dev-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/voidxela/roku-dev-mcp/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.00435 | $0.00435 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
roku-dev-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 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Specification
All implementation work must conform to the design specification in docs/SPEC.md. Read it in full before beginning any task. The spec is the source of truth for architecture, tool definitions, protocol details, error handling, and project structure.
Commit Conventions
Use subject-only conventional commits. The entire commit message is a single line — no body, no footer.
Format: <type>: <subject>
Examples:
feat: add roku_send_keys tool handlerfix: handle empty sgnodes tree responsetest: add integration tests for crash recoveryrefactor: extract digest auth into standalone moduledocs: update SPEC.md with timeout defaultschore: configure tsup build
Allowed types: feat, fix, test, refactor, docs, chore, ci, perf.
Commit completed and validated work promptly. Do not accumulate unrelated changes into a single commit. Each commit should represent a coherent, working unit of change that has been verified before committing.
Testing Requirements
Every implementation task must include appropriate tests. Do not consider work complete until tests are written and passing.
Unit Tests
Write unit tests for all modules, adapters, parsers, and library utilities. Use mocked network responses — unit tests must not require a Roku device. Refer to Section 11.1 of the spec for the required coverage areas per module.
Integration Tests
Write integration tests that run against a real Roku device. These tests are gated behind the ROKU_INTEGRATION_TEST=1 environment variable and must be skipped when it is not set. Refer to Section 11.2 of the spec for the required integration test scenarios.
Integration tests must:
- Use the real Roku protocols (HTTP, Telnet) against a physical device.
- Validate end-to-end behavior, not just mocked interactions.
- Clean up after themselves (e.g., uninstall sideloaded apps when done).
- Have reasonable timeouts appropriate for real hardware latency.
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 · 42 lines · 435 tokens per session scan A d892985b280e
roku-dev-mcp AGENTS.md is an instructions file published in the GitHub repository voidxela/roku-dev-mcp (0 stars, last pushed 5d ago), licensed Unlicense. It adds 435 tokens to every session, about $0.0022 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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.