spiceflow: Instructions file for Codex

AGENTS.md

spiceflow AGENTS.md is an instructions file for Codex, OpenCode from remorses/spiceflow. It costs 7,300 tokens per session, scanned A, original, MIT.

Project instructions for Spiceflow, a pre-release TypeScript framework, and its workspace-based package setup. They explain how generated README files and duplicated consumer repositories are maintained.

In plain words
What is it for?
Updating the source README, rebuilding generated README files, following documentation structure rules, and working with pnpm workspaces and monorepos, which are repositories containing multiple related packages.
Why use it?
They prevent edits to generated files from being lost and keep documentation consistent across the project.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/remorses/spiceflow/agents-md"><img src="https://agentmods.dev/badge/instructions/remorses/spiceflow/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7,300 This file is loaded in full into every session.
When invoked 7,300 The same file — it is already loaded in full.
Security scan A 1 finding. 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.07300 $0.07300
Opus 5.5 $0.02920 $0.02920
Sonnet 5.5 $0.01460 $0.01460
Haiku 4.5 $0.00730 $0.00730

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

Security

Grade A, and why

spiceflow AGENTS.md scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Use Node.js `fetch(baseURL + "/path")` directly (not `page.evaluate`) when you need to control HTTP headers like `Origin` — browsers restrict forbidden headers.
AGENTS.md · 463 lines

How it starts

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

spiceflow is still in pre release. ignore backwards compatibility, instead focus on making code as simple as possible

generated READMEs

The root README.md is the single source of truth. These files are generated from it and must NOT be edited directly:

  • spiceflow/README.md — generated by spiceflow/package.json build script

The website imports the root README.md directly via holocron's local import feature (website/src/index.mdx), so no copy step is needed.

Always edit the root README.md and then rebuild to propagate changes.

README content guidelines

When adding or editing content in the root README.md, follow these rules:

  • Progressive disclosure. Early sections introduce the framework to new users with simple examples. Advanced topics, edge cases, and platform-specific patterns go later in the document.
  • Prescriptive rules in toggles. Paragraphs that say ALWAYS, MUST, Never, or prescribe strict rules for agents/developers should be wrapped in <details><summary>descriptive title</summary>...</details> toggles so they don't dominate the reading flow.
  • Short headings. Keep section headings concise (3-5 words). Move explanatory content into the opening paragraph below the heading.
  • Extend existing examples. For new APIs, prefer adding them to an existing section's code examples rather than creating a new section. Only add a new ## section for a genuinely new core API or concept.
  • Think about placement. Before adding content, review the overall section hierarchy and choose the best location. Don't just append at the end — find the section where the topic fits logically.
  • Split long sections. If a ## section grows beyond ~5 paragraphs or ~3 code blocks, split it into ### subsections with short headings. Readers should never have to scroll through a wall of content under a single heading.

package manager: pnpm with workspace

This project uses pnpm workspaces to manage dependencies. Important scripts are in the root package.json or various packages package.json

Read the full file on GitHub · 463 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. 2mo ago First seen · 463 lines · 7,300 tokens per session scan A 87e706706688

Subscribe to this mod's changes

spiceflow AGENTS.md is an instructions file published in the GitHub repository remorses/spiceflow (169 stars, last pushed 2d ago), licensed MIT. It adds 7,300 tokens to every session, about $0.0292 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

spiceflow AGENTS.md compared with instructions from other repositories

spiceflow AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spiceflow AGENTS.mdremorses/spiceflowInstructions file1692d agoMITA7,300Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode