intuitive-flow: Instructions file for Codex

AGENTS.md

intuitive-flow AGENTS.md is an instructions file for Codex, OpenCode from MiaoDX/intuitive-flow. It costs 527 tokens per session, scanned A, original, MIT.

Project-specific instructions for working on MiaoDX’s intuitive-flow repository. They describe preferred tools, delegation rules, and how development and verification should be organized.

In plain words
What is it for?
Use them when working in the intuitive-flow codebase. They cover environment setup, task delegation, development, testing, and workflow decisions.
Why use it?
They give an agent the repository’s local expectations instead of relying on generic coding habits. They also help keep delegated work and verification consistent with the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Codex; $skill-name invocation.

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

Reuse

Borrowing it

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

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 intuitive-flow AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/miaodx/intuitive-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/miaodx/intuitive-flow/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 527 This file is loaded in full into every session.
When invoked 527 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.00527 $0.00527
Opus 5.5 $0.00211 $0.00211
Sonnet 5.5 $0.00105 $0.00105
Haiku 4.5 $0.00053 $0.00053

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

Security

Grade A, and why

intuitive-flow 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 16d 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 · 25 lines

How it starts

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

Agent Guide

  • Repo-owned skill sources live in skills/; update installed copies through the sync script.
  • Use Bash for orchestration and Bun-run TypeScript for structured scripts. For Python, use uv and the repository .venv; avoid unnecessary dependencies.
  • For web retrieval, use fetch MCP for simple direct reads, Firecrawl for general external pages, and Jina Reader as fallback; follow the retrieval reference.
  • Fail explicitly in code; avoid hasattr() / getattr() for known types.
  • Prefer live-at-HEAD behavior and forward migrations; remove obsolete in-repo APIs and shims unless a bridge is explicitly required.
  • Keep commits atomic with a Co-authored-by: trailer naming the agent that did the work (for example Codex <[email protected]>). Do not amend or force-push unless asked; fetch and rebase if a push is rejected because the remote moved.
  • Explicit user instructions take precedence over skill instructions. If a skill would make you pause, ask, or stop short of the request, name the SKILL.md and quote the instruction.
  • bun run verify checks the repo. scripts/update.sh mutates installed tools and user configuration; it is not a test command.

Task routing

  • Use $intuitive-flow for ordinary execution, $intuitive-reduce-entropy for unknown cleanup targets, and $intuitive-refactor for selected seams.
  • Use $intuitive-preflight for unresolved scope or acceptance decisions; reuse the user's existing authorization.
  • Guidance/setup belongs to $intuitive-init, human docs to $intuitive-doc, test-suite organization to $intuitive-tests, and requested history cleanup to $intuitive-squash.
  • For delegation, read skills/_shared/references/delegation.md; assign disjoint ownership and keep integration and verification in the main session.

Sources of truth

  • Keep README thin. Use ARCHITECTURE for boundaries, STATUS for current commands/state, and docs/human/** for detail, as the task requires.
  • .planning/ holds locked summaries and execution state; archives, generated release notes, and unpromoted specs are historical. Prefer curated planning ingest.
  • Update the owning human doc when runtime truth changes, and active planning summaries when scope or decisions change.
  • Shared rules belong here; CLAUDE.md contains Claude-specific additions. Put reusable procedures in skills and deterministic rules in scripts/hooks.

Read the full file on GitHub · 25 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. 16d ago Changed · +15 tokens per session 725ea2e3b2c1
  2. 1mo ago Changed · +2 lines · +66 tokens per session f05167e4fe9e
  3. 1mo ago Changed · +4 tokens per session e84af60fff79
  4. 1mo ago Changed · -61 lines · -1,001 tokens per session 1fddb6ece02e
  5. 1mo ago Changed · +12 tokens per session d1d76e3ac6da
  6. 1mo ago First seen · 84 lines · 1,431 tokens per session scan A 2b46cd77dd11

Subscribe to this mod's changes

intuitive-flow AGENTS.md is an instructions file published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed 17d ago), licensed MIT. It adds 527 tokens to every session, about $0.0021 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