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/nandomoreirame/forja/agents-mdgit clone --depth 1 https://github.com/nandomoreirame/forjaWrote 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/nandomoreirame/forja/agents-md)<a href="https://agentmods.dev/instructions/nandomoreirame/forja/agents-md"><img src="https://agentmods.dev/badge/instructions/nandomoreirame/forja/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.01905 | $0.01905 |
| Opus 5 | $0.00953 | $0.00953 |
| Sonnet 5 | $0.00381 | $0.00381 |
| Haiku 4.5 | $0.00191 | $0.00191 |
Grade A, and why
forja 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 3d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What is Forja
Forja is a desktop GUI client for Vibe Coders and other AI coding CLIs, built as a pnpm monorepo with Electron + React + TypeScript. It features a hybrid rendering approach with xterm.js for terminal emulation and React for rich markdown/code output.
Status: Active development. v1.9.2. Cross-platform: macOS, Linux, Windows.
Monorepo Structure
pnpm workspaces with apps/* and packages/*:
| Package | Path | Description |
|---|---|---|
@forja/desktop |
apps/desktop/ |
Electron desktop app (main product) |
@forja/site |
apps/site/ |
Next.js 15 marketing site (port 3030) |
@forja/docs |
apps/docs/ |
Fumadocs documentation site (port 3031) |
@forja/mobile |
apps/mobile/ |
Expo remote control app (React Native) |
@forja/tsconfig |
packages/tsconfig/ |
Shared TypeScript configs (base, react, node, nextjs) |
@forja/shared |
packages/shared/ |
Shared types and constants (WebSocket bridge, IPC types) |
All packages reference each other via workspace:* protocol.
Build Commands
# Development (all from monorepo root)
pnpm dev # Desktop app (Vite + Electron concurrently)
pnpm dev:site # Marketing site (Next.js, port 3030)
pnpm dev:docs # Documentation site (Fumadocs, port 3031)
pnpm dev:mobile # Mobile app (Expo)
# Build
pnpm build # Desktop: TypeScript compile + Vite build
pnpm build:electron # Desktop: full Electron build (dmg/AppImage/deb/nsis)
pnpm build:site # Site: Next.js static export
pnpm build:docs # Docs: Next.js build
# Testing
pnpm test # All workspaces (pnpm -r run test)
pnpm test:desktop # Desktop only (multi-project: frontend + electron + scripts)
# Cleanup
pnpm clean # Clean all workspace build artifacts
Running Desktop Tests
# From root (filters to @forja/desktop)
pnpm test:desktop -- path/to/file.test.ts # Specific file
pnpm test:desktop -- --project frontend # Frontend tests only (happy-dom)
pnpm test:desktop -- --project electron # Electron tests only (node)
pnpm test:desktop -- --watch # Watch mode
# From apps/desktop/ directly
pnpm test path/to/file.test.ts
pnpm test --project frontend
pnpm test --reporter=verbose
pnpm test:coverage
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.
- 3d ago First seen · 194 lines · 1,905 tokens per session scan A b11db83e1a50
forja AGENTS.md is an instructions file published in the GitHub repository nandomoreirame/forja (11 stars, last pushed 5mo ago), licensed MIT. It adds 1,905 tokens to every session, about $0.0095 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
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.