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/jetsprow/j-board/agents-mdgit clone --depth 1 https://github.com/JetSprow/J-BoardWrote 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.
[](https://agentmods.dev/instructions/jetsprow/j-board/agents-md)<a href="https://agentmods.dev/instructions/jetsprow/j-board/agents-md"><img src="https://agentmods.dev/badge/instructions/jetsprow/j-board/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00669 | $0.00669 |
| Opus 5 | $0.00334 | $0.00334 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
J-Board 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 4d 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 — 59 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 node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
Repository Notes For Coding Agents
This file is for agents working in this repository. Product, deployment, API, and operations documentation belongs in README.md, docs/API.md, and agent/jboard-agent/README.md.
Project Shape
J-Board is a Next.js App Router application backed by Prisma/PostgreSQL and Redis. It integrates with 3x-ui rather than replacing it:
- J-Board owns users, orders, plans, subscriptions, payments, support, notifications, audit logs, settings, and risk review.
- 3x-ui owns actual inbound runtime configuration and Xray clients.
agent/jboard-agentis a read-only sidecar for latency, route trace, and optional Xray access log telemetry.
Do not add a new node control plane or Xray process manager unless the user explicitly changes the product direction.
Next.js Work
Before editing App Router files, route handlers, server actions, metadata, or caching behavior, read the relevant docs from node_modules/next/dist/docs/ for the installed Next.js version.
Common areas to check:
- App Router file conventions.
- Route Handler request/response behavior.
- Server Actions and
use serverrequirements. - Caching,
revalidatePath, and dynamic rendering rules.
Version And Release Policy
Panel and Agent versions are not forced to move together.
- Website/admin/UI/docs/server-only changes can be committed and pushed to
mainwithout creating a GitHub Release. - Only create a new Agent tag and GitHub Release when Agent code, Agent install/upgrade behavior, or Agent release artifacts change.
- Agent releases must include
jboard-agent-linux-amd64,jboard-agent-linux-arm64, andSHA256SUMS. - Agent runtime version is in
agent/jboard-agent/cmd/agent/main.go. - Agent build version is in
agent/jboard-agent/Makefile. - Panel package version is in
package.jsonand does not need to match the Agent version.
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.
- 4d ago First seen · 59 lines · 669 tokens per session scan A f9fec4af6b6c
J-Board AGENTS.md is an instructions file published in the GitHub repository JetSprow/J-Board (110 stars, last pushed 3mo ago), licensed MIT. It adds 669 tokens to every session, about $0.0033 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.
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.