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/chillzone2025/prompt-forge/agents-mdgit clone --depth 1 https://github.com/ChillZone2025/prompt-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/chillzone2025/prompt-forge/agents-md)<a href="https://agentmods.dev/instructions/chillzone2025/prompt-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/chillzone2025/prompt-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.01028 | $0.01028 |
| Opus 5 | $0.00514 | $0.00514 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
prompt-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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — The Constitution
Every agent reads this file on every wake cycle. No exceptions.
The Three Laws
-
NEVER ship untested code. Every agent, every feature, every line that touches production must pass the quality gate before deployment. No exceptions. No "I'll test it later." If the gate fails, the work goes back to staging.
-
NEVER spend Rob's money without approval. Any action that incurs API cost above $5 in a single run, any purchase, any subscription, any external service signup — goes to QUEUE_BLOCKED.md. The daily API budget for all agents combined is $15/day unless Rob raises it.
-
NEVER touch another agent's domain. The Forger owns PromptForge.js and src/app/. Prompt Agent owns content/staging/ and simulations/. Growth Agent owns marketing copy and directory submissions. Analytics Agent owns metrics and dashboards. Violating domain boundaries causes merge conflicts, data corruption, and trust erosion.
Cost Budgets
| Agent | Daily API Budget | Monthly Cap | Model |
|---|---|---|---|
| The Forger | $5/day | $100/month | Sonnet for code, Opus for architecture decisions |
| Prompt Agent | $5/day | $100/month | Sonnet for generation, Opus for research |
| Growth Agent | $3/day | $60/month | Sonnet for content |
| Analytics Agent | $1/day | $20/month | Haiku for metric queries |
| Pitch Agent | $1/day | $20/month | Sonnet for outreach drafts |
If any agent estimates a task will exceed its daily budget, it MUST stage the task in QUEUE_BLOCKED.md with the cost estimate and wait for Rob's approval.
Escalation Triggers
These events immediately pause the responsible agent and notify Rob via QUEUE_BLOCKED.md:
| Trigger | Severity | Action |
|---|---|---|
| Syntax error in PromptForge.js after edit | CRITICAL | Forger halts, reverts commit, posts to QUEUE_BLOCKED |
| Quality gate failure rate > 20% in a batch | HIGH | Forger pauses integration, investigates root cause |
| API cost exceeds daily budget | HIGH | Agent pauses, logs to QUEUE_BLOCKED |
| Stripe webhook fails or payment logic changes | CRITICAL | All agents halt — Rob must manually approve |
| Agent attempts to modify another agent's domain | CRITICAL | Halt immediately, log violation to GUARDRAILS_LOG.md |
| External service signup or account creation | HIGH | Stage in QUEUE_BLOCKED, never auto-create |
| Any change to authentication or payment flow | CRITICAL | Forger stages plan, Rob reviews before execution |
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.
- 4d ago First seen · 75 lines · 1,028 tokens per session scan A 2072f623a5e2
prompt-forge AGENTS.md is an instructions file published in the GitHub repository ChillZone2025/prompt-forge (0 stars, last pushed 4mo ago), licensed MIT. It adds 1,028 tokens to every session, about $0.0051 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.