agent-forge

Mandatory workflow rules for Agent Forge, a project process that governs how AI agents handle design, coding, testing, and review work.

In plain words
What is it for?
Use it to identify the correct workflow stage, recall prior project context, create a structured plan for substantial work, and record the result at the end.
Why use it?
It prevents agents from skipping required planning, memory, and troubleshooting stages or adding runtime agent code where it is not allowed.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/ontorata/ratary/agent-forge
Clone the repo
git clone --depth 1 https://github.com/ontorata/ratary

Made for: Cursor.

Per session 257 This file is loaded in full into every session.
When invoked 257 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00257 $0.00257
Opus 5 $0.00129 $0.00129
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00026 $0.00026

Measured yesterday against content hash 5789c75f77c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-forge 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 yesterday.

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.

.cursor/rules/agent-forge.mdc · 20 lines

What it actually says

Agent Forge (mandatory)

Before any design, code, test, or review work:

  1. Identify pipeline stage from docs-ai agent-forge workflows / product phase README under docs-ai · NOW.md
  2. Read and follow the matching skill in .cursor/skills/forge-*/SKILL.md (skills remain in the Ratary Cursor workspace)
  3. Run Recall at session start (forge-recall) and Remember at session end (forge-remember) when MCP is available
  4. Do not skip Intent → Isolate → Blueprint for non-trivial features (multi-file or structural)
  5. On failure, switch to forge-diagnose before guessing fixes

Authority: docs-ai Knowledge OS > Agent Forge > ad-hoc prompts.
Legacy prompt IDs: search docs-ai designs/ / governance/ — do not duplicate long prompt text in chat.

Constitution: no agent runtime code in Ratary src/ — Forge is workflow law only.

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. yesterday First seen · 20 lines · 257 tokens per session scan A 5789c75f77c6

Subscribe to this mod's changes

agent-forge is a cursor rule published in the GitHub repository ontorata/ratary (1 stars, last pushed 22d ago), licensed MIT. It adds 257 tokens to every session, about $0.0013 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-31.