Borrowing it
Nothing to install: this file belongs to robcsaszar/ai-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/robcsaszar/ai-forge/main/AGENTS.mdgit clone --depth 1 https://github.com/robcsaszar/ai-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/robcsaszar/ai-forge/agents-md)<a href="https://agentmods.dev/instructions/robcsaszar/ai-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/ai-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/robcsaszar/ai-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/ai-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.01467 | $0.01467 |
| Opus 5.5 | $0.00587 | $0.00587 |
| Sonnet 5.5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
ai-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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Mission
This repo publishes the ai-forge skill pack: eight skills covering the lifecycle of an AI skill or agent definition, create, judge, review, apply, evaluate, recap, update, and audit. There is no build, no tests, no runtime of its own. The deliverable is the contents of skills/*, each copied in from a source repo (Orakl) where they are used and refined, then published here for anyone to install. Changes should be judged by: would a stranger who installs one of these skills into an unrelated project get correct, generic guidance out of it?
Layout convention
- One directory per skill under
skills/<name>/,name:in frontmatter matching the directory name exactly. - Each skill's full directory ships as-is:
SKILL.mdplus anyreferences/,assets/,agents/,evals/, orscripts/it depends on. Don't split a skill across a partial copy. - Three skills ship a
scripts/directory:ai-forge-create/scripts/validate-metadata.cjs,ai-forge-audit/scripts/check-ecosystem.cjs, andai-forge-eval/scripts/aggregate-benchmark.cjs. All are zero-dependency Node scripts with no network calls. SeeSAFETY.mdfor the current, verified description of each. - Skill bodies stay under 200 lines and ~1,800 words. Reference files over 300 lines carry a
## ContentsTOC.
Judgment boundaries
NEVER:
- Never let a copied skill's content leak repo-specific references back to Orakl (or any other single source project). A published skill needs to read as generic guidance, not one project's internal notes.
- Never remove a skill without asking first: the eight here form one lifecycle, and removing one leaves a gap other skills' cross-references (e.g.
ai-forge-auditrequiringai-forge-judge) assume is filled.
ASK:
- Ask before changing the license or copyright holder.
- Ask before adding a ninth skill that doesn't fit the create/judge/review/apply/eval/recap/update/audit lifecycle the other eight cover.
ALWAYS:
- When a skill's
scripts/directory gains, loses, or changes what a script does: updateSAFETY.mdin the same change, based on actually reading the script, not assuming its behavior is unchanged. - When adding, removing, or renaming a skill: update the table in
README.mdin the same change. - Before publishing, run the three pre-publish checks below. All three must be clean.
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 Changed · +29 lines · +418 tokens per session 1508a7076d5e
- 2mo ago First seen · 59 lines · 1,049 tokens per session scan A 41fdad303949
ai-forge AGENTS.md is an instructions file published in the GitHub repository robcsaszar/ai-forge (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,467 tokens to every session, about $0.0059 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.
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).
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.