flameox: Instructions file for Codex

AGENTS.md

flameox AGENTS.md is an instructions file for Codex, OpenCode from morluto/flameox. It costs 600 tokens per session, scanned A, original, MIT.

Repository instructions for flameox, a local evidence system for investigating performance, memory, execution, concurrency, and reliability problems. It preserves profiling and tracing results so an agent or person can inspect and challenge the conclusion.

In plain words
What is it for?
Use it when developing flameox or planning investigations that compare runs, preserve diagnostic artifacts, configure workloads, and distinguish supported, refuted, or inconclusive findings.
Why use it?
It keeps runtime investigations reproducible by linking symptoms to captured evidence, hypotheses, experiments, and conclusions.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 flameox AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/morluto/flameox/agents-md"><img src="https://agentmods.dev/badge/instructions/morluto/flameox/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 600 This file is loaded in full into every session.
When invoked 600 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.00600 $0.00600
Opus 5.5 $0.00240 $0.00240
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

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

Security

Grade A, and why

flameox 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 19d 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 · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Working on Flameox

Flameox is a local runtime-evidence layer for coding agents. It coordinates maintained measurement tools, extracts bounded evidence, and optionally preserves native artifacts and provenance. The agent owns hypotheses and conclusions. There is no workspace initialization or named workload configuration: callers supply exact artifact paths or typed capture targets.

Constraints that affect implementation

  • Keep CLI and MCP thin over AnalysisRuntime and the operation registry. Public fields, bounds, and descriptions belong in canonical runtime models; transport schemas derive from them. Expose named task-shaped tools, without search/execute gateways or aliases.
  • Preserve native bytes, provenance, failed attempts, and experiment structure. Keep observed, derived, and inferred claims distinct; profiles alone do not prove improvement or correctness.
  • Keep work request-owned and scratch ephemeral. Durable evidence uses content-addressed artifacts and immutable authoritative manifests. DuckDB is ephemeral only; Flameox never creates or imports SQLite, though upstream packages may read their native formats internally.
  • Capture takes validated argv, cwd, environment, provider fields, and request-lowerable limits. It runs trusted local programs; process bounds are not a sandbox.
  • Continuations read saved inputs without rerunning workloads. Session handles and durable evidence have different lifetimes; preserve exact continuation and recovery handoffs.

Find the relevant contract

Consult the owning contract when changing that behavior; routine edits do not require reading all docs. Module ownership is in architecture.

Change Contract
Product scope, process or package boundaries Architecture
Preservation, provenance, persisted schemas Storage and evidence
Experiments, metrics, comparisons Investigations
Providers, native formats, compatibility Adapters
Cancellation, resources, integrity, privacy Runtime safety
CLI, MCP, setup, update, continuation Interfaces
Test selection and proof gaps Testing

Read the full file on GitHub · 49 lines

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. 19d ago Changed · -90 lines · -772 tokens per session f3f179dfb234
  2. 20d ago Changed · +11 lines · +125 tokens per session ababaf69be2e
  3. 1mo ago Changed · +4 tokens per session e802203d375c
  4. 1mo ago Changed · +4 lines · +73 tokens per session 36217dadd5b2
  5. 2mo ago First seen · 124 lines · 1,170 tokens per session scan A 3422ea77954f

Subscribe to this mod's changes

flameox AGENTS.md is an instructions file published in the GitHub repository morluto/flameox (227 stars, last pushed 3d ago), licensed MIT. It adds 600 tokens to every session, about $0.0024 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

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,715 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,262 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 · 2,750 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,261 tokens