project-factory: Instructions file for Codex

AGENTS.md

project-factory AGENTS.md is an instructions file for Codex, OpenCode from koldovsky/project-factory. It costs 508 tokens per session, scanned A, original, MIT.

Project-specific instructions for a multi-tool coding-agent plugin that explains its framework differences, required documents, and handoff process.

In plain words
What is it for?
Use them when working on the Project Factory repository. They direct agents to the current project state, capability plan, requirements, framework documentation, and maintenance steps for synchronized skill references.
Why use it?
They tell agents which local sources to read before making substantial changes and warn that the project's framework APIs and structure may differ from familiar versions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions AGENTS.md; mentions Codex.

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

Reuse

Borrowing it

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

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 project-factory AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/koldovsky/project-factory/agents-md"><img src="https://agentmods.dev/badge/instructions/koldovsky/project-factory/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 508 This file is loaded in full into every session.
When invoked 508 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.00508 $0.00508
Opus 5.5 $0.00203 $0.00203
Sonnet 5.5 $0.00102 $0.00102
Haiku 4.5 $0.00051 $0.00051

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

Security

Grade A, and why

project-factory 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 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.

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

This is NOT the Next.js you know

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.

This repo is a multi-tool plugin (Claude Code · Cursor · Codex · Copilot), with AGENTS.md + the project-factory skill as the portable core. See docs/portability.md and the README for install per tool.

Maintaining the skill: skills/project-factory/ is self-contained — its references/ holds generated mirrors of the canonical orchestration docs (MASTER-PROMPT.md, LOOP.md, checklists/quality-gates.md, commands/{init,onboard}.md). After editing any of those, run node scripts/sync-skill-refs.mjs to refresh the mirrors. --check fails if they are stale (wire it into CI if you add one).

Use docs/requirements.md to understand the requirements for the project.

Project Handoff Protocol

Before planning or implementing any substantive change, read:

  1. docs/current-state.md for the latest persistent handoff and next-step guidance.
  2. docs/mvp-capability-plan.md for the MVP change sequence and capability scope.
  3. openspec/project.md and the relevant files under openspec/specs/ for current accepted behavior.
  4. docs/adr/ for accepted architecture decisions.

Keep docs/current-state.md current when a meaningful milestone happens, especially when:

  • an OpenSpec change is created, implemented, validated, or archived;
  • a capability moves from planned to implemented;
  • setup instructions, validation expectations, or known blockers change;
  • architectural decisions are accepted or replaced.

docs/current-state.md is a handoff aid, not the source of truth. If it conflicts with code, OpenSpec specs, ADRs, or tests, verify the repo state and update the handoff file.

Write last update date/time and the current phase of the project in the file (use Kyiv time zone). Example:

- **Date and time:** 2026-04-29 16:40:00
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 · 44 lines · 508 tokens per session scan A 5dccd27d8cd8

Subscribe to this mod's changes

project-factory AGENTS.md is an instructions file published in the GitHub repository koldovsky/project-factory (10 stars, last pushed 1mo ago), licensed MIT. It adds 508 tokens to every session, about $0.0020 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-31.

Related

project-factory AGENTS.md compared with instructions from other repositories

project-factory AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
project-factory AGENTS.mdkoldovsky/project-factoryInstructions file101mo agoMITA508Codex, 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