nifra: Instructions file for Codex

AGENTS.md

nifra AGENTS.md is an instructions file for Codex, OpenCode from nifrajs/nifra. It costs 2,703 tokens per session, scanned A, original, MIT.

A quick reference for coding agents working with Nifra, a TypeScript framework for building typed web applications that run on Bun and other runtimes. It shows how to define routes, validate incoming data, read platform settings, and set response details.

In plain words
What is it for?
Use it to add typed API routes, validate request bodies and queries, read environment values and platform services, set status codes or headers, and run Nifra checks.
Why use it?
It gives agents copy-ready patterns and project-specific rules without requiring them to search through the framework source. It also describes checks that can confirm whether the work is complete.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is nifrajs/nifra's own configuration. It tells Codex and OpenCode how to work on nifra 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 nifra configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nifrajs/nifra. 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/nifrajs/nifra/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/nifrajs/nifra

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 nifra AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nifrajs/nifra/agents-md"><img src="https://agentmods.dev/badge/instructions/nifrajs/nifra/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,703 This file is loaded in full into every session.
When invoked 2,703 The same file — it is already loaded in full.
Security scan A 1 finding. 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.02703 $0.02703
Opus 5.5 $0.01081 $0.01081
Sonnet 5.5 $0.00541 $0.00541
Haiku 4.5 $0.00270 $0.00270

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

Security

Grade A, and why

nifra AGENTS.md scanned grade A with 1 finding 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 10d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

`env` is forwarded from `app.fetch(request, { env })` (Workers bindings). Validate at the boundary.
AGENTS.md · 178 lines

How it starts

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

AGENTS.md - Nifra quick reference for coding agents

Nifra is a Bun-native, multi-runtime, end-to-end-typed full-stack TS framework. This is the copy-paste cookbook so you don't have to read the source. Deeper docs live in docs/ and at /docs/contract. Machine surfaces for agents: nifra check --json (the done-gate), nifra context, and the MCP server (nifra mcp).

1 · Define a route (typed, chainable)

import { server } from "@nifrajs/core/server"

export const app = server()
  .get("/users/:id", (c) => ({ id: c.params.id })) // c.params typed from the path literal
  .get("/files/*path", (c) => ({ path: c.params.path })) // trailing wildcard

Return a value → serialized to JSON. Return a Response → used as-is.

2 · Validate a body/query at the trust boundary (auto-422)

import { t } from "@nifrajs/schema"

app.post(
  "/users",
  { body: t.object({ name: t.string({ minLength: 1 }), age: t.number() }) },
  (c) => ({ id: crypto.randomUUID(), name: c.body.name }), // c.body is typed + already validated
)

t.object rejects unknown fields by default (additionalProperties: false) → a structured 422 with { path: [...] } issues before the handler runs. Need to allow extras? t.looseObject. Query schema: { query: t.object({…}) } → c.query.

3 · Read platform env (KV / D1 / secrets)

// Type it ONCE on server<Env>() → c.env is typed everywhere below (no per-binding cast).
const app = server<{ MY_KV: KVNamespace; API_SECRET: string }>().get(
  "/x",
  (c) => c.env.API_SECRET, // c.env: Env  (it's `unknown` if you don't pass <Env>)
)

env is forwarded from app.fetch(request, { env }) (Workers bindings). Validate at the boundary.

4 · Set status / headers, and the control-flow rule

app.post("/things", { body: t.object({ name: t.string() }) }, (c) => {
  c.set.status = 201
  c.set.headers["x-created"] = "1"
  return { ok: true }
})

For full control, return a Response. Throw rule: throw new Response("", { status: 404 }) = an intentional HTTP response (control flow - bypasses _error); throw new Error(…) = the nearest _error boundary / a 500.

Read the full file on GitHub · 178 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. 10d ago Changed · +11 lines · +195 tokens per session 8f6c84b777fd
  2. 11d ago Changed · +2 lines · +41 tokens per session a8625e8c9faf
  3. 17d ago Changed · +8 lines · +115 tokens per session 9a7a59d21de3
  4. 1mo ago First seen · 157 lines · 2,352 tokens per session scan A fd2895d9edc4

Subscribe to this mod's changes

nifra AGENTS.md is an instructions file published in the GitHub repository nifrajs/nifra (5 stars, last pushed yesterday), licensed MIT. It adds 2,703 tokens to every session, about $0.0108 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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,649 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,549 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,731 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