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/mundizzle/mun.digital/agents-mdgit clone --depth 1 https://github.com/mundizzle/mun.digitalWhat 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.01072 | $0.01072 |
| Opus 5 | $0.00536 | $0.00536 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
mun.digital 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 apps/web/node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
mun.digital Agent Rules
This file is only for durable rules needed to plan and code correctly in this repo.
Project State
- Major portfolio features should use their own Git branch and PR.
- Do not add status snapshots, history, roadmaps, task lists, or decision logs to this file.
- Keep task-specific plans, status, and implementation notes in the active PR or the issue/discussion context provided by the user.
Stack
- Use pnpm.
- Keep local development on Node
24via.nvmrc. Inpackage.json, use the broadest safe minimum Node engine for the published CLI so newer Node versions do not warn unnecessarily. - Use Next.js App Router, TypeScript, and Tailwind.
- Before writing Next-specific code, check the relevant docs in
apps/web/node_modules/next/dist/docs/; this repo uses Next 16 and some conventions differ from older examples. - Use
apps/web/src/proxy.tsfor Next 16 request interception. Do not add deprecatedmiddleware.ts.
Local Skills
- Use OpenSpec for spec-driven code changes. Start with
/opsx:proposefor new changes, follow the generated OpenSpec artifacts through implementation, and archive completed changes when appropriate. - Use locally installed skills when creating functionality, writing code, reviewing code, or deploying this repo.
- For web UI, HTML, CSS, browser APIs, or client-side JavaScript, follow the installed web guidance skills before coding.
- For React or Next.js work, follow the installed React, Next.js, and Vercel React best-practice skills in addition to the local Next 16 docs.
- For deployment, Vercel configuration, Vercel deployment environment variables, or preview/production releases, follow the installed Vercel deployment skills.
- If a relevant skill is unavailable in the current session, note that and continue with the repo rules and official docs.
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 · 79 lines · 1,072 tokens per session scan A 79c23fe05b78
mun.digital AGENTS.md is an instructions file published in the GitHub repository mundizzle/mun.digital (0 stars, last pushed 3d ago), licensed MIT. It adds 1,072 tokens to every session, about $0.0054 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-31.
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).
spec-kit AGENTS.md
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.
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.
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.
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).
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.