.opencode

A set of rules for the .opencode directory, which contains configuration and commands for OpenCode AI tools. The directory is treated as separate, read-only tool configuration.

In plain words
What is it for?
Use it when reviewing or working around OpenCode settings and commands, while keeping them out of code reviews, commits, and the main development workflow.
Why use it?
It prevents tool-specific files from being changed, copied into application code, or mistaken for project development guidance.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/rshade/finfocus/opencode
Clone the repo
git clone --depth 1 https://github.com/rshade/finfocus

Made for: GitHub Copilot.

Per session 184 This file is loaded in full into every session.
When invoked 184 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00184 $0.00184
Opus 5 $0.00092 $0.00092
Sonnet 5 $0.00037 $0.00037
Haiku 4.5 $0.00018 $0.00018

Measured yesterday against content hash ff6c6c0e31fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.github/instructions/.opencode.instructions.md · 30 lines

What it actually says

OpenCode Directory Instructions

This directory contains OpenCode AI-specific configuration and commands. These files are used by OpenCode AI tools and should not be modified or referenced in the main codebase.

Guidelines for this directory:

  • Do not modify any files in this directory
  • Do not reference files from this directory in code
  • Do not commit changes to files in this directory
  • Do not copy content from this directory to other locations

Purpose:

  • OpenCode AI tool configuration
  • AI-specific command definitions
  • OpenCode workspace settings
  • AI tool integration files

When working with OpenCode files:

  • Treat as read-only configuration
  • Do not use as reference for main codebase patterns
  • Ignore for code review and analysis
  • Keep separate from development workflow
Changes

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.

  1. yesterday First seen · 30 lines · 184 tokens per session scan A ff6c6c0e31fe

Subscribe to this mod's changes

.opencode is an instructions file published in the GitHub repository rshade/finfocus (5 stars, last pushed 15d ago), licensed Apache-2.0. It adds 184 tokens to every session, about $0.0009 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.

Related

Other instructions, from other repositories

costory-finops-mcp-skills AGENTS.md

AGENTS.md instructions for costory-io/costory-finops-mcp-skills, covering agents.md — conventions for ai coding agents in this repo, layout, skill id mapping (costory mcp), when changing a skill and when adding a new skill.

costory-io/costory-finops-mcp-skills · 1,611 tokens

ai-pricing-hub-mcp CLAUDE.md

Claude Code instructions for OptimNow/ai-pricing-hub-mcp, covering claude.md - ai pricing hub mcp app, what this project does, architecture, data sources and the fallback chain and project structure.

OptimNow/ai-pricing-hub-mcp · 7,347 tokens

ai-pricing-hub-mcp AGENTS.md

AGENTS.md instructions for OptimNow/ai-pricing-hub-mcp: Before writing code, first explore the project structure, then invoke the chatgpt-app-builder skill for documentation.

OptimNow/ai-pricing-hub-mcp · 22 tokens

insideout-power AGENTS.md

Instructions for luthersystems/insideout-power, covering insideout — riley infrastructure agent, what riley can do for you, how to invoke riley, via remote mcp (preferred — use this first) and via agent skills.

luthersystems/insideout-power · 1,155 tokens

cloud-mcp-server CLAUDE.md

Claude Code instructions for alexei-led/cloud-mcp-server, covering aws mcp server development guide, build & test commands, architecture, server (server.py) and sandbox (sandbox.py).

alexei-led/cloud-mcp-server · 1,114 tokens

devopness AGENTS.md

Instructions for devopness/devopness, covering agents, core flow, shared constraints, monorepo structure and git workflow.

devopness/devopness · 570 tokens