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/opsyhq/opsy/claude-mdgit clone --depth 1 https://github.com/opsyhq/opsyWrote 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/opsyhq/opsy/claude-md)<a href="https://agentmods.dev/instructions/opsyhq/opsy/claude-md"><img src="https://agentmods.dev/badge/instructions/opsyhq/opsy/claude-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.1 | $0.00404 | $0.00404 |
| Opus 5 | $0.00202 | $0.00202 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
opsy CLAUDE.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 5d 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.
What it actually says
Claude Instructions
The idea of AGENTS.md, distilled — see it for the full rationale. Two failure modes drive everything below: baked-in answers and drift (parallel sources of truth that look equivalent today and diverge tomorrow).
-
Dynamic behavior. No hard-coded hacks, static maps, aliases, fallbacks, or one-off exceptions to steer product behavior. It comes from source-of-truth: runtime discovery, provider APIs, DB state, schemas, tools, config. If something is wrong, fix the dynamic path — never bake the answer in.
-
One source of truth. Don't invent wrapper types, copied API shapes, or parallel ownership when an existing schema/contract/DB row/domain type fits — tighten the existing type instead. Don't re-run the same validation across route/service/workflow/step; validate once at the boundary that owns the decision and pass typed state forward.
-
Minimal structure. Don't extract trivial transforms, predicates, or key builders into helpers unless they encode a real reusable concept or remove meaningful duplication — otherwise inline them. Prefer direct functional flow; treat
letclusters, broad casts,Awaited<ReturnType<…>>, and prepare/derive scaffolding as smells. -
Flow ownership. One public function owns a domain flow. Don't hide branching behind vague orchestration (
ensure*,hydrate*,prepare*,resolve*). If it's "read, if missing or stale generate/sync, read again," write that sequence directly in the owning function. -
Migrations. Generate with
bun run db:generate --name <name>fromapps/api; apply withbun run db:migratefromapps/api. No hand-rolled structural DDL — only data backfills the generator can't infer.
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.
- 5d ago First seen · 33 lines · 404 tokens per session scan A bcbd5fd28bf6
opsy CLAUDE.md is an instructions file published in the GitHub repository opsyhq/opsy (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 404 tokens to every session, about $0.0020 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-30.
Other instructions, from other repositories
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.
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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).