Borrowing it
Nothing to install: this file belongs to zhangqi444/open-forge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zhangqi444/open-forge/main/AGENTS.mdgit clone --depth 1 https://github.com/zhangqi444/open-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/zhangqi444/open-forge/agents-md)<a href="https://agentmods.dev/instructions/zhangqi444/open-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/zhangqi444/open-forge/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.
<a href="https://agentmods.dev/instructions/zhangqi444/open-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/zhangqi444/open-forge/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01700 | $0.01700 |
| Opus 5.5 | $0.00680 | $0.00680 |
| Sonnet 5.5 | $0.00340 | $0.00340 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
open-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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
agents.md compatibility — this file orients any AI coding agent (Claude Code, Codex, Cursor, Aider, Continue.dev, OpenClaw, Hermes-Agent, or a custom tools-using LLM) that's working on the open-forge codebase. End users using the open-forge skill to deploy software should look at SKILL.md instead.
Canonical reference. This file is intentionally short. The full architectural treatment, strict-doc-verification policy, two-tier coverage model, sanitization rules, and issue-processing workflow live in CLAUDE.md. Read that for the complete picture — AGENTS.md is the agents.md-standard landing page that points at it.
What this project is
open-forge is a guided self-hosting skill distributed via Claude Code's plugin marketplace and adapted for 6+ other AI platforms. It walks users from "I have a cloud account and a domain" to "working app at https://my.domain" via a phased workflow (preflight → provision → dns → tls → smtp → inbound → hardening → feedback) using 2,200+ verified recipes plus curated bundles for goal-shaped requests (AI homelab, privacy stack) plus a live-derived fallback for the long tail.
This isn't a typical software repo — it's a library of platform-agnostic markdown recipes + a thin Bash build script. There's no compiled artifact, no test suite, no lint config. The "build" is regenerating distribution bundles from canonical sources.
Working on this repo — the rules
Per CLAUDE.md:
- No human PRs — issues only. Catalog evolves through GitHub issues processed by AI sessions. See
.github/ISSUE_TEMPLATE/for the three input channels (recipe-feedback, software-nomination, method-proposal). Direct PRs are discouraged; if you submit one, the strict-doc policy still applies. - Strict-doc-verification policy. Every install method in every recipe must cite an upstream URL (
> **Source:** <url>). Community-maintained methods open with the required ⚠️ blockquote. The README is necessary but not sufficient — also read the upstream docs site, repodocs/install/tree, and wiki. If upstream-doc fetch fails, stop; do not write speculative content. Full rules in CLAUDE.md § Strict doc-verification policy. - Sanitization principles. User-shared content (deploy logs, gotchas, error output) must be stripped of identifiers (domains, IPs, SSH keys, API keys, AWS account IDs, emails) before being merged into recipes or posted to GitHub issues. Full strip-list with regex patterns in CLAUDE.md § Sanitization principles.
- Two-tier coverage model. Tier 1 = verified recipes in
references/projects/. Tier 2 = live-derived from upstream docs at runtime for software not yet in the catalog. Promotion criteria in CLAUDE.md § Two-tier coverage model. - In-scope test. Before adding a recipe: deployable service / static-site generator / CLI agent / AI inference server / CI runner / storage backend → ✅. Library / desktop app / SaaS-only → ❌. Decision rule + edge-case table in CLAUDE.md § Is this software in scope?.
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.
- 1mo ago First seen · 82 lines · 1,700 tokens per session scan A ba8ed95bf155
open-forge AGENTS.md is an instructions file published in the GitHub repository zhangqi444/open-forge (97 stars, last pushed 4mo ago), licensed MIT. It adds 1,700 tokens to every session, about $0.0068 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-30.
Other instructions, from other repositories
ai-agent-rules-generator ui-design.instructions.md
Glitch Payment Gateway admin UI design rules — mandatory element & component reference for WooCommerce settings.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).