website AGENTS.md

Repository instructions for kagent-dev/website, including a warning that its version of Next.js, a web application framework, has breaking changes and project-specific documentation.

In plain words
What is it for?
Finding the correct local Next.js documentation and following the repository’s rules when developing or maintaining the website.
Why use it?
They prevent an agent from relying on familiar but outdated Next.js behavior when changing the website.

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

Made for: Codex, OpenCode.

Per session 154 This file is loaded in full into every session.
When invoked 154 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00154 $0.00154
Opus 5 $0.00077 $0.00077
Sonnet 5 $0.00031 $0.00031
Haiku 4.5 $0.00015 $0.00015

Measured yesterday against content hash 63f2c50380ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

website 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 yesterday.

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.

Origin

This is a copy

100% identical to ui-beats AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 10 lines

What it actually says

This is NOT the Next.js you know

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices.

This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.

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. yesterday First seen · 10 lines · 154 tokens per session scan A 63f2c50380ed

Subscribe to this mod's changes

website AGENTS.md is an instructions file published in the GitHub repository kagent-dev/website (19 stars, last pushed 3d ago), licensed Apache-2.0. It adds 154 tokens to every session, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ui-beats AGENTS.md, differing in 0 lines, and is treated as a copy.