oc-flue-starter: Instructions file for Codex

AGENTS.md

oc-flue-starter AGENTS.md is an instructions file for Codex, OpenCode from diggerhq/oc-flue-starter. It costs 280 tokens per session, scanned A, original, MIT.

Repository instructions for an OpenComputer Flue starter app, including its product guidance, deployment setup, skills, runtime tools and validation commands. Flue is the app framework used by this project.

In plain words
What is it for?
Use them when changing the app's public examples, agent skills, model setting, health route, build files or deployment configuration.
Why use it?
They prevent changes that would misrepresent the starter app or rely on files and settings that are not available after deployment. They also record required checks before deployment.

Instructions file for CodexOpenCode

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

This is diggerhq/oc-flue-starter's own configuration. It tells Codex and OpenCode how to work on oc-flue-starter 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 oc-flue-starter configures →

Reuse

Borrowing it

Nothing to install: this file belongs to diggerhq/oc-flue-starter. 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/diggerhq/oc-flue-starter/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/diggerhq/oc-flue-starter

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 oc-flue-starter AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/diggerhq/oc-flue-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/diggerhq/oc-flue-starter/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 280 This file is loaded in full into every session.
When invoked 280 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.00280 $0.00280
Opus 5.5 $0.00112 $0.00112
Sonnet 5.5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

oc-flue-starter 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 · 19 lines

What it actually says

Working on this starter

This is a stock Flue app deployed to OpenComputer with oc agent deploy. Read PRODUCT.md before changing its public positioning or examples.

  • Keep agent.toml model aligned with @opencomputer/flue's DEFAULT_MODEL.
  • Never commit credentials or generated dist/, .flue-vite/ or .wrangler/ output.
  • Custom tools run in the deployed app. Import every runtime fixture; do not read the git checkout by path.
  • Agent-owned skills are packaged imports: SKILL.md plus with { type: 'skill' }, then skills: [...]. Do not claim they are copied into a workspace.
  • The default example intentionally has no sandbox:. Add ocSandbox(ctx.env) only for a feature that genuinely needs shell/files, and keep repo workspace support out until it is implemented.
  • Keep src/app.ts exporting @opencomputer/flue/app; its /health route is part of deploy activation.
  • Reserved OC_ and FLUE_ names belong to the platform.
  • Keep every README command pasteable in zsh and every demo prompt consistent with src/data/orders.json.

Validate with npm run typecheck and npm run build. Deploy with oc agent deploy.

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 · 19 lines · 280 tokens per session scan A e101c00ccd8d

Subscribe to this mod's changes

oc-flue-starter AGENTS.md is an instructions file published in the GitHub repository diggerhq/oc-flue-starter (2 stars, last pushed 3mo ago), licensed MIT. It adds 280 tokens to every session, about $0.0011 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.

Related

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

microsoft/vscode · 9,719 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,516 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 3,093 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,313 tokens