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/andreinicu/world-forge/agents-mdgit clone --depth 1 https://github.com/AndreiNicu/World-ForgeWrote 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/andreinicu/world-forge/agents-md)<a href="https://agentmods.dev/instructions/andreinicu/world-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/andreinicu/world-forge/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.01734 | $0.01734 |
| Opus 5 | $0.00867 | $0.00867 |
| Sonnet 5 | $0.00347 | $0.00347 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
World-Forge 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — standing instructions for agentic tools
Read this first. It applies to Kilo Code, Cline, and any other agentic IDE tool opening this workspace. It is deliberately short — it routes you to the right document for your session type instead of duplicating them.
First: which kind of session is this?
A. Running the pipeline (most sessions)
The user typed /worldforge brainstorm, /worldforge start, /worldforge revise,
/worldforge resync-preset, /worldforge convert, or a resume/skip/status variant.
- Open
workflows/world-forge.mdand follow it. It is the router and the source of truth for what runs when: it dispatches build runs to four stage files (world-forge-discovery.md→world-forge-drafting.md→world-forge-validation.md→world-forge-construction.md). Load the router plus the active stage file only — never all of them. Revise runs live inworkflows/world-forge-revise.md, convert runs inworkflows/world-forge-convert.md, and preset resync / audition / post-launch routing inworkflows/world-forge-postlaunch.md. - Kilo Code Subagent Delegation: If you are the top-level Kilo Code agent, do not run the pipeline commands inline. Instead, use your subagent delegation tool (e.g., the
tasktool) to route the command to the correct custom subagent:/worldforge brainstormor/world-forge brainstorm→ Dispatch toWorldForge-Brainstormer(optional ideation upstream of Phase 0; writes informalBrainstorm_Notes.md, no World Seed)/worldforge startor/world-forge start→ Dispatch toWorldForge-Interviewer/worldforge reviseor/world-forge revise(with--freeform,--target, etc.) → Dispatch toWorldForge-Reviser/worldforge convertor/world-forge convert→ Dispatch toWorldForge-Converter/worldforge resume phase[N]→ Dispatch to the custom agent defined for Phase N (e.g.,WorldForge-Editorfor Phase 3)
- If a dispatch or model call fails, never do the phase's work inline. Retry the
dispatch; if it stays unavailable, set the Pipeline State Ledger
statustoBLOCKED, halt, and surface it to the user (router → DISPATCH PROTOCOL rule 1). An inline-produced phase has no agent spec, no Context Manifest, and no valid sign-off — treat its output as if the phase never ran. - Pipeline files are READ-ONLY at runtime: everything under
agent_roles/,templates/,workflows/, plusNotes_On_functionality.mdandNotes_Quick_Reference.md. You write only to the world project'sDrafts/,Export/,World_Seed.md, and report files. If you find yourself about to edit a pipeline file mid-run, stop and surface it to the user — an agent went off-script. - Load only what each phase needs. Every agent spec begins with a
📂 CONTEXT MANIFESTlisting exactly what to load. Honor it. In particular, never loadSamples/,wiki/,CLAUDE.md,CHANGELOG.md, ortutorial.mdduring a run — they are human-facing or maintenance material and only burn context. - For SillyTavern runtime questions (position values, lorebook flags, token budget,
prompt assembly order): consult
Notes_Quick_Reference.mdfirst. Open the fullNotes_On_functionality.mdonly when the quick reference does not settle the question or the agent spec explicitly requires a section of it.
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 · 107 lines · 1,734 tokens per session scan A b0413e209d21
World-Forge AGENTS.md is an instructions file published in the GitHub repository AndreiNicu/World-Forge (72 stars, last pushed 1mo ago), licensed MIT. It adds 1,734 tokens to every session, about $0.0087 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
fount AGENTS.md
AGENTS.md instructions for steve02081504/fount, covering fount architecture & ai agent guide, core principles, system overview, dev guidelines and specialized guides.
show-me-the-story AGENTS.md
AGENTS.md instructions for Nigh/show-me-the-story, covering agents.md — ai 小说生成器项目指南, 项目概述, 编译与运行, 完整编译（含前端构建） and 或手动分步.
story-skills AGENTS.md
AGENTS.md instructions for danjdewhurst/story-skills, covering agent instructions, project overview, development commands, implementation rules and skill authoring.
super-agent-party AGENTS.md
AGENTS.md instructions for heshengtao/super-agent-party, covering super agent party 项目上下文, 项目概述, 技术栈, 目录结构速查 and 架构要点.
Risuai AGENTS.md
AGENTS.md instructions for kwaroran/Risuai, covering project overview, directory structure, source code structure (/src), building and running and prerequisites.
arcvellum AGENTS.md
AGENTS.md instructions for o-1717986918/arcvellum, covering agents, product boundary, development entry, worker constitution and verification.