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.
npx agentmods add instructions/remorses/spiceflow/agents-mdgit clone --depth 1 https://github.com/remorses/spiceflowWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.07300 | $0.07300 |
| Opus 5 | $0.03650 | $0.03650 |
| Sonnet 5 | $0.01460 | $0.01460 |
| Haiku 4.5 | $0.00730 | $0.00730 |
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 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.
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. 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 byspiceflow/package.jsonbuild 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
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.
- 2d ago First seen · 463 lines · 7,300 tokens per session scan A 87e706706688
spiceflow AGENTS.md is an instructions file published in the GitHub repository remorses/spiceflow (167 stars, last pushed 9d ago), licensed MIT. It adds 7,300 tokens to every session, about $0.0365 per session on Opus 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.
Other instructions, from other repositories
my-first-mcp copilot-instructions.md
Copilot instructions for sethdavis512/my-first-mcp, covering github copilot instructions, analysis of index.js (2025-07-10), code patterns, best practices and style guidelines.
vuestrata AGENTS.md
Instructions for boussadjra/vuestrata, covering using vite+, the unified toolchain for the web, built-in commands vs scripts, tool versions, review checklist and vuestrata project rules.
pinyin AGENTS.md
Instructions for yunsii/pinyin, covering agents.md, hard rules, 方案与文本靠 side-effect 注册，漏 import 等于没加, vite.config.ts 的 base: '/pinyin/' 不要随手改 and 拼音术语变量名用全拼.
vite-ts-react-template CLAUDE.md
Instructions for bartstc/vite-ts-react-template, covering project, stack, commands, core principles and workflow.
vite-ts-react-template tests.instructions.md
Instructions for bartstc/vite-ts-react-template, covering testing, tools, ai boundaries and test priorities.
vite-ts-react-template workflow.instructions.md
Instructions for bartstc/vite-ts-react-template, covering workflow, scanning repository, anchor comments and implementation.