ocawe AGENTS.md

Repository instructions for developing Ocawe, a framework for declarative workflows and HTTP services. They define the framework areas, design rules, testing expectations, documentation updates, and commit format.

In plain words
What is it for?
Changing workflow execution, schemas, registries, HTTP endpoints, runtime wiring, documentation, specifications, and release commits.
Why use it?
They reduce the risk that changes will make runtime behavior unpredictable, break API responses, or leave code, tests, and documentation out of sync.

Instructions file for CodexOpenCode

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/lefinepro/ocawe/agents-md
Clone the repo
git clone --depth 1 https://github.com/lefinepro/ocawe

Made for: Codex, OpenCode.

Per session 382 This file is loaded in full into every session.
When invoked 382 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.00382 $0.00382
Opus 5 $0.00191 $0.00191
Sonnet 5 $0.00076 $0.00076
Haiku 4.5 $0.00038 $0.00038

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

Security

Grade A, and why

ocawe 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 2d 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 · 44 lines

What it actually says

Ocawe Framework Development Agent Guide

Goal

Develop and evolve Ocawe framework internals safely and consistently.

Scope

  • Runtime engine and declarative workflow API
  • NodeKind execution model
  • Registry surface (Ocawe::RegistryApi.node_kind, Ocawe::RegistryApi.resource)
  • HTTP runtime endpoints and compatibility behavior
  • Type-safe schema/DSL integration

Core Rules

  1. Keep runtime behavior deterministic.
  2. Prefer additive API changes; avoid hidden implicit behavior.
  3. Preserve error envelope consistency for HTTP APIs.
  4. Keep NodeKind execution explicit and testable.
  5. Add/update specs with every behavior change.
  6. Don't use any

Architecture Focus

  • Declarative runtime: src/framework/workflows/declarative
  • DSL/schema: src/framework/workflows/dsl
  • Registry API: src/framework/registry/api.cr
  • HTTP app/endpoints: src/framework/http

Change Checklist

  1. Update code and types.
  2. Update runtime wiring/boot paths.
  3. Update docs in packages/docs/guides.
  4. Add or adjust specs under spec/.
  5. Validate no stale API names remain.

Commit Instructions

  • Analyze the project changes and make a commit with conventional commits format.
  • Make a commit explaining why the changes were made and what's new.
  • Commit only changed files, not all files, and do not add new files unless they were added manually.

API Direction

  • Use Workflow#step(type, id, ...) as the unified node entry for built-in and external nodes.
  • For NodeKind steps use Workflow#step(Ocawe::NodeKind.new(...), id: ...).
  • Register node kinds only via Ocawe::RegistryApi.node_kind.
  • Register resource handlers only via Ocawe::RegistryApi.resource.
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. 2d ago First seen · 44 lines · 382 tokens per session scan A e26b951acc1d

Subscribe to this mod's changes

ocawe AGENTS.md is an instructions file published in the GitHub repository lefinepro/ocawe (11 stars, last pushed 2d ago), licensed 0BSD. It adds 382 tokens to every session, about $0.0019 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.