mcpforwork: Instructions file for Codex

AGENTS.md

mcpforwork AGENTS.md is an instructions file for Codex, OpenCode from avivancos/mcpforwork. It costs 1,977 tokens per session, scanned A, original, Apache-2.0.

A repository instruction file that tells coding agents and contributors which product rules, architecture choices, testing methods, and backlog steps to follow.

In plain words
What is it for?
Use it to guide agent-assisted development, enforce product boundaries, organize work through a backlog, and keep tests and contributions consistent.
Why use it?
It gives everyone one shared set of rules, reducing conflicting changes and missed requirements. TDD means writing a failing test first, then code to pass it; zero mocks means tests use real or recorded dependencies instead of fake substitutes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is avivancos/mcpforwork's own configuration. It tells Codex and OpenCode how to work on mcpforwork itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcpforwork configures →

Reuse

Borrowing it

Nothing to install: this file belongs to avivancos/mcpforwork. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/avivancos/mcpforwork/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/avivancos/mcpforwork

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for mcpforwork AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/avivancos/mcpforwork/agents-md/github.svg)](https://agentmods.dev/instructions/avivancos/mcpforwork/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/avivancos/mcpforwork/agents-md"><img src="https://agentmods.dev/badge/instructions/avivancos/mcpforwork/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.

agentmods 80×15 button for mcpforwork AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/avivancos/mcpforwork/agents-md"><img src="https://agentmods.dev/badge/instructions/avivancos/mcpforwork/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,977 This file is loaded in full into every session.
When invoked 1,977 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01977 $0.01977
Opus 5.5 $0.00791 $0.00791
Sonnet 5.5 $0.00395 $0.00395
Haiku 4.5 $0.00198 $0.00198

Measured 2mo ago against content hash ba0ba44e4ba9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcpforwork 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 2mo 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 · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — source of truth for all agents and contributors

Everything here binds every coding agent (Claude Code, Codex, Cursor) and every human contributor. CLAUDE.md only adds Claude-Code-specific notes; on conflict, this file wins. All prose, code, comments, and docs are English-only.

The full product specification lives in docs/PRODUCT_PLAN.md. Section references such as "§Architecture spec" point there.


1. Product invariants (never violate)

  1. The LLM is the client. No server-side LLM calls, ever. No openai/anthropic SDK importable from domain/, services/, ports/, or packs/ — enforced by import-linter in CI.
  2. Graduated autonomy, consent-based. Never submit without a recorded consent check: request_submit is the only place a submit directive can be issued, and consent artifacts (L1 approval, L2 policy) are written exclusively by the human-session HTTP API — never by an MCP tool (ADR 0005). Supervised (L0) is the default.
  3. Open-core. Every feature works self-hosted on SQLite with no account. Hosted-only concerns (Postgres/RLS, Stripe, mailer) live behind ports.
  4. Never fabricate. Every generation brief includes a facts inventory; drafts may only claim what the profile proves. Gaps are acknowledged, never stuffed.
  5. Sector/country logic is data, not code. Site knowledge ships as versioned packs in packs/, updatable independently of releases.
  6. User owns their data. Export/delete paths are mandatory for any new personal-data table; EEO data is optional and privacy-gated.

2. Architecture (pragmatic hexagonal)

src/mcpforwork/
  domain/       # PURE logic, no I/O; imports nothing from any other layer
  services/     # use cases; signatures (uow, user_id, ...); caller commits;
                # consent + caps + dedup gates live here
  ports/        # typing.Protocol seams ONLY: Database/UoW, Mailer, Billing,
                # FileStore, Clock
  adapters/     # driven implementations: db/{sqlite,postgres}, billing, mail, files
  entrypoints/  # driving, all thin (auth + serialization only): mcp, api, cli
  packs/        # DATA not code: country/sector source packs + schema validator

Read the full file on GitHub · 160 lines

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. 2mo ago First seen · 160 lines · 1,977 tokens per session scan A ba0ba44e4ba9

Subscribe to this mod's changes

mcpforwork AGENTS.md is an instructions file published in the GitHub repository avivancos/mcpforwork (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 1,977 tokens to every session, about $0.0079 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

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.

denoland/deno · 3,077 tokens