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/guillermoscript/lms-front/agents-mdgit clone --depth 1 https://github.com/guillermoscript/lms-frontWrote 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/guillermoscript/lms-front/agents-md)<a href="https://agentmods.dev/instructions/guillermoscript/lms-front/agents-md"><img src="https://agentmods.dev/badge/instructions/guillermoscript/lms-front/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.05987 | $0.05987 |
| Opus 5 | $0.02993 | $0.02993 |
| Sonnet 5 | $0.01197 | $0.01197 |
| Haiku 4.5 | $0.00599 | $0.00599 |
Grade A, and why
lms-front 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 yesterday.
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 — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
LMS V2 is a modern Learning Management System built with Next.js 16 and Supabase. This is a complete rebuild prioritizing exceptional UX for students and teachers. The project uses Row Level Security (RLS) for direct database queries instead of server actions for CRUD operations.
Key Technologies:
- Next.js 16.1.5 (App Router, React 19)
- Supabase (PostgreSQL 15, Auth, Storage)
- Shadcn UI (base-mira theme)
- Tailwind CSS v4
- TypeScript (strict mode)
- Stripe for payments
Commands
Development
npm run dev # Start development server at http://localhost:3000
npm run build # Build for production (checks TypeScript/lint errors)
npm run start # Start production server
npm run lint # Run ESLint
Database (Supabase)
supabase db pull # Pull schema from cloud
supabase db push # Push migrations to cloud
supabase migration new <name> # Create new migration file
Important: Database migrations are in supabase/migrations/. The database has 44 tables with comprehensive RLS policies.
Available Skills
This project has custom Claude Code skills available in skills/:
/web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use this skill when:
- Reviewing UI implementations
- Checking accessibility compliance
- Auditing design patterns
- Ensuring best practices for web interfaces
Usage:
/web-design-guidelines app/dashboard/student/page.tsx
/web-design-guidelines "app/dashboard/**/*.tsx"
This skill fetches the latest Web Interface Guidelines and validates code against them, reporting findings in file:line format.
MCP Integration
This project includes a Model Context Protocol (MCP) server that allows AI assistants like Claude to interact with the LMS database through secure, authenticated tools.
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.
- yesterday First seen · 526 lines · 5,987 tokens per session scan A f23018b4537b
lms-front AGENTS.md is an instructions file published in the GitHub repository guillermoscript/lms-front (25 stars, last pushed 2d ago), licensed MIT. It adds 5,987 tokens to every session, about $0.0299 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-09-03.
Other instructions, from other repositories
skillsboard AGENTS.md
AGENTS.md instructions for TommyBez/skillsboard, covering agents.md, cursor cloud specific instructions, what this is, running locally and database schema.
prest copilot-instructions.md
Copilot instructions for prest/prest, covering copilot instructions for prest go backend, project scope, core engineering principles, solid principles for go and s — single responsibility.
pg_exporter AGENTS.md
Instructions for nbari/pg_exporter, covering agents.md, project shape, first steps, devpod workflow (preferred) and local commands.
counterpoise-ledger CLAUDE.md
Instructions for jeffjjohnston/counterpoise-ledger, covering claude.md, project overview, development commands, essential commands and testing.
mcp-database CLAUDE.md
Claude Code instructions for DiegoBulhoes/mcp-database, covering claude.md, commands, architecture, invariants (do not weaken) and adding or changing a tool.
spasm-forum-server AGENTS.md
Instructions for spasm-network/spasm-forum-server, a project described as: Backend for Spasm-powered forum.