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/mori-shin-x/fullstack-bun-sample/agents-mdgit clone --depth 1 https://github.com/mori-shin-x/fullstack-bun-sampleWrote 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/mori-shin-x/fullstack-bun-sample/agents-md)<a href="https://agentmods.dev/instructions/mori-shin-x/fullstack-bun-sample/agents-md"><img src="https://agentmods.dev/badge/instructions/mori-shin-x/fullstack-bun-sample/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.01600 | $0.01600 |
| Opus 5 | $0.00800 | $0.00800 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
fullstack-bun-sample 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is a Bun fullstack dev server + Elysia sample.
Tech stack
- Runtime/bundler: Bun (HTML imports,
bun build,bun --hot) - Server: Elysia (Bun-backed)
- Client: React 19 + TanStack Router (file-based) + Tanstack Query
- Styling: Tailwind CSS v4 + tw-animate (animation utilities)
- UI primitives: Radix UI + lucide-react (shadcn/ui-style, local component copies)
Directory tree (annotated)
Curated tree (not exhaustive) focusing on key areas:
.
├── AGENTS.md
├── README.md
├── bunfig.toml
├── build.ts
├── Dockerfile
├── cloudbuild.yaml
├── src/ # application source
│ ├── server.ts
│ ├── server/ # Elysia app and API features
│ │ ├── app.ts
│ │ └── features/ # API modules per feature
│ │ └── <feature>/ # feature namespace
│ │ ├── routes.ts
│ │ └── service.ts
│ ├── public/ # static public assets
│ │ └── index.html
│ ├── main.tsx
│ ├── routes/ # TanStack Router file routes
│ │ └── **/*.tsx
│ ├── routeTree.gen.ts
│ ├── client/ # client-side app modules
│ │ ├── app/ # providers, router, query setup
│ │ ├── components/ # shared UI components
│ │ ├── features/ # client feature logic
│ │ ├── infra/ # client infrastructure
│ │ │ └── api/ # Eden client + helpers
│ │ └── styles/ # Tailwind source styles
│ │ └── global.css
│ └── shared/ # shared types/data
└── dist/ # build output
Project map
src/server.ts: server entry; servesindex.htmlfor/and SPA fallback; API under/api/*.src/server/app.ts: Elysia app, error handling, feature route registration.src/server/features/**: API modules (e.g.routes.ts,service.ts).src/public/index.html: HTML entry (imports../main.tsx).src/main.tsx: React entry; renders providers and router.src/routes/**: TanStack Router file routes (UI-level route components).src/routeTree.gen.ts: generated router tree; do not edit. Runbun run generate-root.src/client/app/**: Tanstack Query + Router providers and setup.src/client/features/**: UI logic per feature/route.src/client/infra/api/**: Eden client + helpers (unwrapfor Tanstack Query).src/client/components/**: shared UI components.src/client/styles/global.css: Tailwind source (compiled at build time).src/shared/**: shared types/data for server + client.dist/: build output (index.html,index-*.js,index-*.css,server.js).
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.
- 3d ago First seen · 174 lines · 1,600 tokens per session scan A 9a61740b9cde
fullstack-bun-sample AGENTS.md is an instructions file published in the GitHub repository mori-shin-x/fullstack-bun-sample (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,600 tokens to every session, about $0.0080 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.