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/yuqie6/productflow/agents-mdgit clone --depth 1 https://github.com/yuqie6/ProductFlowWrote 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.
[](https://agentmods.dev/instructions/yuqie6/productflow/agents-md)<a href="https://agentmods.dev/instructions/yuqie6/productflow/agents-md"><img src="https://agentmods.dev/badge/instructions/yuqie6/productflow/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01190 | $0.01190 |
| Opus 5 | $0.00595 | $0.00595 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
ProductFlow 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trellis Instructions
These instructions are for AI assistants working in this project.
This project is managed by Trellis. The working knowledge you need lives under .trellis/:
.trellis/workflow.md— development phases, when to create tasks, skill routing.trellis/spec/— package- and layer-scoped coding guidelines (read before writing code in a given layer).trellis/workspace/— per-developer journals and session traces.trellis/tasks/— active and archived tasks (PRDs, research, jsonl context)
If a Trellis command is available on your platform (e.g. /trellis:finish-work, /trellis:continue), prefer it over manual steps. Not every platform exposes every command.
If you're using Codex or another agent-capable tool, additional project-scoped helpers may live in:
.agents/skills/— reusable Trellis skills.codex/agents/— optional custom subagents
Managed by Trellis. Edits outside this block are preserved; edits inside may be overwritten by a future trellis update.
Repository Guidelines
Project Structure & Module Organization
ProductFlow is a private single-merchant workspace. The backend lives in backend/src/productflow_backend/ and uses clear layers: presentation/ for FastAPI routes and schemas, application/ for use cases, domain/ for enums/core concepts, and infrastructure/ for database, storage, queues, text/image providers, and poster rendering. Alembic migrations are in backend/alembic/versions/; backend tests are in backend/tests/. The React/Vite app lives in web/src/, with pages in web/src/pages/, shared UI in web/src/components/, and API/type helpers in web/src/lib/. Product and architecture notes live in docs/.
Build, Test, and Development Commands
Use the root justfile whenever possible:
just backend-install— install backend dependencies withuvdev extras.docker compose up -d— start local PostgreSQL and Redis.just backend-migrate— apply Alembic migrations with dev env vars.just backend-run— run the FastAPI API on the dev port.just backend-worker— run Dramatiq workers for async jobs.just backend-test— run backend pytest tests.just web-install— install frontend dependencies with pnpm.just web-dev— run Vite with the API proxy configured.just web-build— type-check and build the frontend.
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.
- 5d ago First seen · 73 lines · 1,190 tokens per session scan A 225a564e6307
ProductFlow AGENTS.md is an instructions file published in the GitHub repository yuqie6/ProductFlow (300 stars, last pushed 3d ago), licensed MIT. It adds 1,190 tokens to every session, about $0.0060 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.
Other instructions, from other repositories
e-commerce-agents CLAUDE.md
Claude Code instructions for nitin27may/e-commerce-agents, covering claude.md, what this is, working artifacts location, key commands and start everything from scratch (one command).
e-commerce-agents AGENTS.md
AGENTS.md instructions for nitin27may/e-commerce-agents: Guidance for AI coding agents (Codex, etc.) working in this repository.
GooFish-AIMonitor AGENTS.md
Instructions for tristanwqy/GooFish-AIMonitor, covering agents.md — 给 ai 协作者的工程指南, 黄金规则(先读这条), 验证命令(完成前必跑), 代码地图 and 数据模型要点.
mcpelevator CLAUDE.md
Instructions for pacnpal/mcpelevator, covering commands, architecture, conventions, agent skills and issue tracker.
mcpelevator AGENTS.md
Instructions for pacnpal/mcpelevator, covering commands, architecture and conventions.
dealwatcher AGENTS.md
AGENTS.md instructions for xiaojiou176-open/dealwatcher, covering dealwatcher agents, identity, non-negotiables, runtime truth and expected working areas.