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/wyattowalsh/agentsWrote 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/wyattowalsh/agents/opencode)<a href="https://agentmods.dev/rules/wyattowalsh/agents/opencode"><img src="https://agentmods.dev/badge/rules/wyattowalsh/agents/opencode/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/wyattowalsh/agents/opencode"><img src="https://agentmods.dev/badge/rules/wyattowalsh/agents/opencode.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.03039 | $0.03039 |
| Opus 5.5 | $0.01216 | $0.01216 |
| Sonnet 5.5 | $0.00608 | $0.00608 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
opencode 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Global Instructions
OpenCode-Specific Overrides
Model Preference
OpenCode model defaults are repo-managed. Repo and live OpenCode config set root model: "openai/gpt-5.5", root small_model: "openai/gpt-5.4-mini", and built-in agents build, plan, explore, and general to openai/gpt-5.5 with variant xhigh. Use the model plus variant fields for high-level thinking; do not invent composite model IDs such as openai/gpt-5.5-high unless the provider metadata defines that exact model. Do not generate OpenAI, Vercel, Kimi, or other remote provider blocks unless a concrete runtime need is verified. OpenCode's built-in provider registry should own normal model definitions; the only repo-managed exception is a minimal xai provider block with empty options so the desktop model picker can select Grok routes without inheriting incompatible OpenAI options. The sync tooling strips vercel/opencode-go/kimi-for-coding entries on every write of the project opencode.json and the live ~/.config/opencode/opencode.json, and sanitizes any xai.options back to {}. This prevents auto-persisted blocks for picker-chosen models from accumulating keys that the target provider rejects ("invalid xai provider options" etc.). Preserve explicit local provider blocks such as LM Studio only when rendered from local provider policy. Do not define duplicate gpt-5.5-fast entries unless concrete runtime evidence requires them. Do not silently fall back to another OpenAI model when CLI/TUI runs warn or retry; compare --pure, plugin-loaded, TUI, and desktop paths first and keep exact request IDs from any server_error lines.
Using Grok 4.3 (or other xai/vercel routes): Use the TUI model picker (<leader>m / model list + variant list). After exercising a new remote route, re-run the normal opencode sync (wagents or equivalent) so the tooling can scrub transient provider blocks and reduce provider.xai to empty options. The OpenAI block remains the only repo-managed provider entry with model variants and plugin options.
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 · 164 lines · 3,039 tokens per session scan A 43f7f7f91c6e
opencode is a cursor rule published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 3,039 tokens to every session, about $0.0122 per session on Opus 5.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
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.