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/sadanandpai/clearfrontend/agents-mdgit clone --depth 1 https://github.com/sadanandpai/clearfrontendWrote 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/sadanandpai/clearfrontend/agents-md)<a href="https://agentmods.dev/instructions/sadanandpai/clearfrontend/agents-md"><img src="https://agentmods.dev/badge/instructions/sadanandpai/clearfrontend/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.01550 | $0.01550 |
| Opus 5 | $0.00775 | $0.00775 |
| Sonnet 5 | $0.00310 | $0.00310 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
clearfrontend 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clearfrontend CLAUDE.md — 88% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClearFrontend — Agent Instructions
Cross-agent compatibility file (OpenAI Codex, GitHub Copilot, and others). Claude Code reads
CLAUDE.mdat root — both files contain identical content.
Project Overview
ClearFrontend is a Next.js 15 coding challenge platform where users solve JavaScript/TypeScript problems and get instant feedback. Code is executed server-side inside a true V8 isolate (isolated-vm + esbuild). The backend uses Appwrite (auth + database), Redis (caching), and Vercel (deployment).
Tech Stack
| Layer | Technology |
|---|---|
| Framework | Next.js 15 (App Router), React 19 |
| Language | TypeScript 7 (strict) |
| Styling | Tailwind CSS v4 + SCSS Modules + Radix UI Themes |
| State | Zustand 5 (Immer), React Query 5 |
| Editor | Monaco Editor (@monaco-editor/react) |
| Execution | isolated-vm 6 + esbuild 0.28 |
| Backend | Appwrite (BaaS) + ioredis |
| Testing | Vitest 4 |
Key Paths
src/app/ Pages and layouts (Next.js App Router)
src/server/ Server-only code — never imported by client components
actions/ Next.js Server Actions ("use server")
data-access/ DB queries (Appwrite / Redis)
services/ External service clients
src/ui/ React components and client-side code
components/core/ Reusable atoms (no domain knowledge)
components/common/ Layout and navigation
components/modules/ Feature-specific components
store/ Zustand stores
context/ React context providers
src/common/ Zero-dependency shared code (types, challenge data, routes)
challenges/ Challenge definitions ({id}.ts)
types/ Shared TypeScript types
scripts/ CLI utilities (validate-challenges.js)
Server Actions Rules
- Always
"use server"at the top of action files. - Validate all inputs — use
isValidChallengeId()for challenge IDs. - Never expose raw DB or internal errors to the client.
- Pattern: validate → authorize → data-access → return.
- Use
respondWithErrorfor structured error responses.
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 · 130 lines · 1,550 tokens per session scan A 58b36bf49080
clearfrontend AGENTS.md is an instructions file published in the GitHub repository sadanandpai/clearfrontend (200 stars, last pushed 11d ago), licensed MIT. It adds 1,550 tokens to every session, about $0.0077 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.