Borrowing it
Nothing to install: this file belongs to t1112000/tutor-management-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/t1112000/tutor-management-app/main/AGENTS.mdgit clone --depth 1 https://github.com/t1112000/tutor-management-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/t1112000/tutor-management-app/agents-md)<a href="https://agentmods.dev/instructions/t1112000/tutor-management-app/agents-md"><img src="https://agentmods.dev/badge/instructions/t1112000/tutor-management-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.1 | $0.00514 | $0.00514 |
| Opus 5 | $0.00257 | $0.00257 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
tutor-management-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 7d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/app/ holds Next.js routes and pages, including (auth) and (dashboard) route groups plus API routes in src/app/api/. UI components live in src/components/, shared helpers in src/lib/, and reusable hooks in src/hooks/. Database models are in src/lib/db/models/, with migrations in src/migrations/. Static or generated assets should stay near the feature that uses them.
Build, Test, and Development Commands
yarn dev: start the Next.js development server.yarn build: create a production build.yarn lint: run ESLint checks.yarn db:migrate: apply pending database migrations.yarn db:migrate:undo: roll back the last migration.yarn set-password: set a user password through the CLI.
There are no automated tests in this repository, so yarn lint and yarn build are the main validation steps before a change is shared.
Coding Style & Naming Conventions
Use TypeScript, functional React components, and the existing Next.js App Router patterns. Keep files and directories descriptive and feature-based, such as src/components/students/StudentsClient.tsx or src/app/(dashboard)/calendar/page.tsx. Follow the repository’s ESLint rules and match the established formatting style in nearby code. Use HH:MM strings for time values and Vietnam time helpers from src/lib/time.ts instead of raw Date logic.
Testing Guidelines
No test framework is configured. When changing behavior, verify the affected flow manually and run yarn lint plus yarn build. If you add tests later, place them near the feature or under a dedicated test directory and use clear names that describe the user-facing behavior.
Commit & Pull Request Guidelines
Recent commits use Conventional Commits with scopes, for example feat(calendar): ... and fix(bills): .... Keep commit messages short, imperative, and scoped when useful. Pull requests should summarize the change, note any database or env updates, and include screenshots for UI changes when relevant.
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.
- 7d ago First seen · 33 lines · 514 tokens per session scan A bca8b9399b24
tutor-management-app AGENTS.md is an instructions file published in the GitHub repository t1112000/tutor-management-app (106 stars, last pushed 7d ago), licensed MIT. It adds 514 tokens to every session, about $0.0026 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.