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/casemark/casedotdev-starter-app/agents-mdgit clone --depth 1 https://github.com/CaseMark/casedotdev-starter-appWrote 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/casemark/casedotdev-starter-app/agents-md)<a href="https://agentmods.dev/instructions/casemark/casedotdev-starter-app/agents-md"><img src="https://agentmods.dev/badge/instructions/casemark/casedotdev-starter-app/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.01597 | $0.01597 |
| Opus 5 | $0.00798 | $0.00798 |
| Sonnet 5 | $0.00319 | $0.00319 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
casedotdev-starter-app 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This document provides comprehensive guidance for AI agents working on the create-legal-app starter kit.
Project Overview
This is a Next.js 15+ starter kit designed specifically for building legal tech applications with AI agent assistance. The codebase is structured to be agent-friendly with clear conventions, comprehensive documentation, and a well-defined architecture.
Core Principles
- Clarity: Every file, function, and component should have a clear, single purpose
- Consistency: Follow established patterns throughout the codebase
- Documentation: Maintain SKILL.md files for each major area of functionality
- Type Safety: Use TypeScript strictly, avoid
anytypes - Agent-Friendly: Structure code and documentation to accelerate AI-assisted development
Tech Stack
- Framework: Next.js 15+ (App Router)
- Language: TypeScript
- UI Library: Shadcn UI (Maia theme preset)
- Icons: Phosphor Icons
- Font: Inter
- Styling: Tailwind CSS with CSS variables
- Runtime: Bun
- Database: Neon (PostgreSQL)
- ORM: Drizzle
- Authentication: Auth.js / WorkOS
- AI: Vercel AI SDK 6
- Payments: Stripe
- SDK: Case.dev SDK
Project Structure
/
├── app/ # Next.js App Router pages and layouts
├── components/ # React components
│ ├── ui/ # Shadcn UI components
│ └── ... # Custom components
├── lib/ # Utility functions and shared code
├── public/ # Static assets
├── skills/ # SKILL.md documentation files
├── AGENTS.md # This file - agent guidance
└── package.json
Design System
This project uses the Maia preset from Shadcn UI with the following configuration:
- Base: Base (neutral foundation)
- Style: Maia
- Base Color: Neutral
- Theme: Neutral
- Icon Library: Phosphor
- Font: Inter
- Menu Accent: Subtle
- Radius: Default
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 · 236 lines · 1,597 tokens per session scan A 888e9f9b7f33
casedotdev-starter-app AGENTS.md is an instructions file published in the GitHub repository CaseMark/casedotdev-starter-app (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,597 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.