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/tech4idea/viforge/agents-mdgit clone --depth 1 https://github.com/tech4idea/viforgeWhat 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.01036 | $0.01036 |
| Opus 5 | $0.00518 | $0.00518 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
viforge 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is the current viforge implementation for sitcom creation workflows. Future agents should treat the monorepo implementation and docs/current/ as the source of truth, not the historical Express starter files that still exist in the repository.
Read First
- Start with
docs/current/README.md. - Use the feature documents in
docs/current/for architecture, workspace filesystem behavior, editor preview behavior, chat sessions, Codex runtime integration, skills/config, WeChat integration, and test commands. - Shared request and response contracts live in
packages/shared/src/contracts.ts; update them before changing either side of an API boundary.
Current Documentation Map
docs/current/01-architecture-and-contracts.md: architecture and shared contracts.docs/current/02-workspace-filesystem.md: workspace filesystem behavior.docs/current/03-web-workbench-ui.md: web workbench UI behavior.docs/current/04-editor-preview.md: editor preview behavior.docs/current/05-chat-agent-sessions.md: assistant chat, sessions, and references.docs/current/06-codex-agent-runtime.md: historical Codex runtime notes.docs/current/07-skills-and-agent-config.md: Agent Skills and agent configuration.docs/current/08-wechat-integration.md: remote WeChat integration.docs/current/09-tests-and-dev-commands.md: tests and development commands.docs/current/11-langgraph-agent-runtime.md: LangGraph Agent runtime.docs/current/18-standalone-desktop-plan.md: standalone desktop implementation plan.docs/current/19-desktop-release-guide.md: desktop build and release guide.docs/current/20-private-binary-bundle-github-actions.md: private binary bundle and GitHub Actions packaging plan.docs/current/21-project-architecture-diagram.html: project architecture diagram.docs/current/22-project-architecture-wireframe.md: project architecture wireframe draft.docs/current/23-agent-harness-functional-boundary.md: Agent Harness current functional boundary.docs/current/24-markdown-annotation-design.md: Markdown annotation design.docs/current/25-agent-harness-runtime-config-prd.md: Agent Harness runtime config PRD.docs/current/26-agent-harness-runtime-config-interaction.html: Agent Harness runtime config interaction draft.
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.
- 2d ago First seen · 81 lines · 1,036 tokens per session scan A 5a562fad46b8
viforge AGENTS.md is an instructions file published in the GitHub repository tech4idea/viforge (78 stars, last pushed 1mo ago), licensed MIT. It adds 1,036 tokens to every session, about $0.0052 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.