opsy: Instructions file for Codex

AGENTS.md

opsy AGENTS.md is an instructions file for Codex, OpenCode from opsyhq/opsy. It costs 431 tokens per session, scanned A, original, Apache-2.0.

A set of coding instructions for opsyhq/opsy, a project for managing infrastructure used by AI agents. It guides code toward dynamic, source-based behavior and reuse of existing data structures.

In plain words
What is it for?
Use it when changing opsy code and you need rules for handling provider data, databases, schemas, services, types, and data flow.
Why use it?
It helps prevent fragile fixes that only work for one case, duplicated data definitions, and unnecessarily complicated code.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is opsyhq/opsy's own configuration. It tells Codex and OpenCode how to work on opsy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opsy configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opsyhq/opsy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/opsyhq/opsy/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/opsyhq/opsy

Made for: Codex, OpenCode.

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

agentmods badge for opsy AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/opsyhq/opsy/agents-md/github.svg)](https://agentmods.dev/instructions/opsyhq/opsy/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/opsyhq/opsy/agents-md"><img src="https://agentmods.dev/badge/instructions/opsyhq/opsy/agents-md/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.

agentmods 80×15 button for opsy AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/opsyhq/opsy/agents-md"><img src="https://agentmods.dev/badge/instructions/opsyhq/opsy/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 431 This file is loaded in full into every session.
When invoked 431 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00431 $0.00431
Opus 5.5 $0.00172 $0.00172
Sonnet 5.5 $0.00086 $0.00086
Haiku 4.5 $0.00043 $0.00043

Measured 2mo ago against content hash 2453599ff2ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

opsy 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 2mo 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.

AGENTS.md · 12 lines

What it actually says

Agent Instructions

  • Do not alter product behavior with hard-coded hacks, static semantic maps, aliases, fallbacks, or one-off exceptions.
  • Keep behavior dynamic: use source-of-truth data, runtime discovery, provider APIs, database state, schemas, tools, and explicit configuration.
  • If something is wrong, improve the dynamic path instead of baking the answer into code.
  • Do not extract trivial one-line transformations, predicates, key builders, or field reshaping into standalone helpers. Inline them where used unless they encode a real reusable domain concept or remove meaningful duplication.
  • Do not invent local wrapper types, copied API shapes, semantic aliases, or ownership structures when an existing schema, provider, contract, DB row type, or exported domain type can be reused. Prefer tightening the existing source-of-truth type over adding a parallel one.
  • Prefer direct functional data flow over mutable assembly. Treat clusters of let, broad casts, Awaited<ReturnType<...>>, and "prepare/derive" scaffolding as smells to simplify unless the code genuinely needs staged ownership.
  • Domain flow must be owned by one public service function. Do not hide branching domain behavior behind vague orchestration helpers named ensure*, hydrate*, prepare*, resolve*, or similar. If a flow is "read, if missing or stale then generate/sync/upsert, then read again", write that sequence directly in the owning function.
  • Do not duplicate validation across route, service, workflow, and step boundaries. Put validation at the earliest boundary that owns the decision, pass typed state forward, and let downstream code handle only real source-of-truth races or failures instead of re-running the same validation.
  • For database schema changes, use the repo migration workflow. Generate migrations with the package script (for API: bun run db:generate --name <name> from apps/api) and apply them with the package migrate script (for API: bun run db:migrate from apps/api). Do not hand-roll structural DDL; only add explicit data backfills/rewrites that the generator cannot infer.
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. 2mo ago First seen · 12 lines · 431 tokens per session scan A 2453599ff2ae

Subscribe to this mod's changes

opsy AGENTS.md is an instructions file published in the GitHub repository opsyhq/opsy (24 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 431 tokens to every session, about $0.0017 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-30.

Related

opsy AGENTS.md compared with instructions from other repositories

opsy AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
opsy AGENTS.mdopsyhq/opsyInstructions file244mo agoApache-2.0A431Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode