agentmods.dev

forge AGENTS.md

Project instructions for Forge, a development framework used to guide coding work through shared methods, commands, and conventions.

In plain words
What is it for?
Use them when building, testing, type-checking, linting, or changing the Forge framework and its public interface.
Why use it?
They give contributors one place to check how the repository works, which commands to run, and which coding rules and sensitive areas to respect.

Instructions file for CodexOpenCode

13 1mo ago A scan 357 tokens original MIT
View the source file firatcand/forge
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 instructions/firatcand/forge/agents-md
Clone the repo
git clone --depth 1 https://github.com/firatcand/forge

Made for: Codex, OpenCode.

Per session 357 This file is loaded in full into every session.
When invoked 357 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.00357 $0.00357
Opus 5 $0.00179 $0.00179
Sonnet 5 $0.00071 $0.00071
Haiku 4.5 $0.00036 $0.00036

Measured 2d ago against content hash ba7c537acc4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

AGENTS.md · 38 lines

What it actually says

This project uses Forge. Before any work, read .forge/CONTEXT.md for the methodology this project follows. If that file is missing, install Forge with:

npm install -g @firatcand/forge
forge upgrade

Note: .forge/CONTEXT.md is gitignored and regenerated per-developer by forge upgrade.

forge

Note: This is the forge repo itself. Iterating on this repo means iterating on the framework — every change ships to npm publish @firatcand/forge and lands on adopter machines via npx @firatcand/forge. Treat all changes as public-API.

Stack

Commands

  • Build: npm run build
  • Test: npm test
  • Type check: npm run typecheck
  • Lint: npm run lint (ESLint — unused vars/imports + unreachable; non-blocking, warnings only)
  • Dev: npm run dev
  • Render methodology context (one-shot, until Phase B's forge upgrade ships): npm run forge:render-context

Conventions

  • Functional components only, no class components
  • Always handle errors explicitly — no silent catches
  • New API routes must have input validation
  • See spec/ for full conventions

Critical paths

See CRITICAL.md

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. 2d ago First seen · 38 lines · 357 tokens per session scan A ba7c537acc4d

Subscribe to this mod's changes

forge AGENTS.md is an instructions file published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 357 tokens to every session, about $0.0018 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.

PlanningTestingagentic-codingai-coding-agentclaude-codecodexcompound-engineeringspec-driven-development
Related

Other instructions, from other repositories

prospec AGENTS.md

Instructions for benwu95/prospec, covering prospec, tech stack, language policy, core resources and constitution.

benwu95/prospec · 2,508 tokens

prospec CLAUDE.md

Instructions for benwu95/prospec, covering prospec, tech stack, language policy, core resources and constitution.

benwu95/prospec · 1,131 tokens

odin-reflector AGENTS.md

Instructions for OutlineDriven/odin-reflector, covering codex reflector agent notes, surface split, model routing invariants, python claude/cursor plugin invariants and omp native extension invariants.

OutlineDriven/odin-reflector · 3,750 tokens

nextjs-loop-engineering-starter AGENTS.md

Instructions for muzafferkadir/nextjs-loop-engineering-starter, covering agents.md — project instructions for ai agents, how to start a loop, project purpose, stack and commands.

muzafferkadir/nextjs-loop-engineering-starter · 1,479 tokens

baro AGENTS.md

AGENTS.md instructions for jigjoy-ai/baro, covering claude.md, project overview, tech stack, directory structure and build commands.

jigjoy-ai/baro · 575 tokens

baro CLAUDE.md

Claude Code instructions for jigjoy-ai/baro, covering claude.md, project overview, tech stack, directory structure and build commands.

jigjoy-ai/baro · 713 tokens