nex AGENTS.md

Project instructions for the Nex web framework, including its coding conventions and the expected shape of requests handled by pages and APIs. Nex is a web framework with request handlers for pages and server endpoints.

In plain words
What is it for?
Use them when changing Nex pages or APIs, reading query or body values, following commit and changelog rules, or configuring a Nex project.
Why use it?
They keep framework changes consistent and prevent agents from using request-handling patterns from incompatible Next.js router styles.

Instructions file for CodexOpenCode

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/gofenix/nex/agents-md
Clone the repo
git clone --depth 1 https://github.com/gofenix/nex

Made for: Codex, OpenCode.

Per session 565 This file is loaded in full into every session.
When invoked 565 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.00565 $0.00565
Opus 5 $0.00282 $0.00282
Sonnet 5 $0.00113 $0.00113
Haiku 4.5 $0.00056 $0.00056

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

Security

Grade A, and why

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

AGENTS.md · 64 lines

How it starts

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

Nex Framework — AI Agent Guide

7. Commit Convention

Follow Conventional Commits:

  • Format: <type>(<scope>): <subject>
  • Subject: ≤50 chars, imperative mood
  • NO triple backticks in commit messages

8. Additional Rules

  • English Only: All code, comments, docs, commits in English
  • Changelog First: Update changelog before any framework change
  • No Config Files: Use .env only, never config/*.exs
  • Cursor Rules: If project has .cursorrules, follow it (see bestof_ex/.cursorrules)

9. Nex Request Contract

  • Canonical Request Type: Page Actions in src/pages/ receive Nex.Req.
  • API Consistency: API Handlers in src/api/ also receive Nex.Req.
  • Comparison Target: Model Nex request handling after Next.js Pages Router API Routes.
  • Parameter Access: Read path params and query string values from req.query. Read request body values from req.body.
  • Do Not Model After: Do not model Page Actions after App Router Route Handlers, Server Actions, FormData-first handlers, or a flat merged params map.
  • Keep The Contract Visible: When the request argument is unused, prefer _req, not _params.

Example:

def save(req) do
  id = req.query["id"]
  name = req.body["name"]

  {:ok, %{id: id, name: name}}
end

Source Code Reference

Source code for dependencies is available in opensrc/ for deeper understanding of implementation details.

See opensrc/sources.json for the list of available packages and their versions.

Use this source code when you need to understand how a package works internally, not just its types/interface.

Fetching Additional Source Code

To fetch source code for a package or repository you need to understand, run:

npx opensrc <package>           # npm package (e.g., npx opensrc zod)
npx opensrc pypi:<package>      # Python package (e.g., npx opensrc pypi:requests)
npx opensrc crates:<package>    # Rust crate (e.g., npx opensrc crates:serde)
npx opensrc <owner>/<repo>      # GitHub repo (e.g., npx opensrc vercel/ai)

Read the full file on GitHub · 64 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. 3d ago First seen · 64 lines · 565 tokens per session scan A f8d05b22b44b

Subscribe to this mod's changes

nex AGENTS.md is an instructions file published in the GitHub repository gofenix/nex (106 stars, last pushed 2mo ago), licensed MIT. It adds 565 tokens to every session, about $0.0028 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.