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/smithaker10/webdev101/copilot-instructionsgit clone --depth 1 https://github.com/Smithaker10/webdev101What 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.01699 | $0.01699 |
| Opus 5 | $0.00849 | $0.00849 |
| Sonnet 5 | $0.00340 | $0.00340 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
webdev101 copilot-instructions.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.
This is a copy
89% identical to ai-website-cloner-template copilot-instructions.md — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
Website Reverse-Engineer Template
What This Is
A reusable template for reverse-engineering any website into a clean, modern Next.js codebase using AI coding agents. The Next.js + shadcn/ui + Tailwind v4 base is pre-scaffolded — just run /clone-website <url1> [<url2> ...].
Tech Stack
- Framework: Next.js 16 (App Router, React 19, TypeScript strict)
- UI: shadcn/ui (Radix primitives, Tailwind CSS v4,
cn()utility) - Icons: Lucide React (default — will be replaced/supplemented by extracted SVGs)
- Styling: Tailwind CSS v4 with oklch design tokens
- Deployment: Vercel
Commands
npm run dev— Start dev servernpm run build— Production buildnpm run lint— ESLint checknpm run typecheck— TypeScript checknpm run check— Run lint + typecheck + build
Code Style
- TypeScript strict mode, no
any - Named exports, PascalCase components, camelCase utils
- Tailwind utility classes, no inline styles
- 2-space indentation
- Responsive: mobile-first
Design Principles
- Pixel-perfect emulation — match the target's spacing, colors, typography exactly
- No personal aesthetic changes during emulation phase — match 1:1 first, customize later
- Real content — use actual text and assets from the target site, not placeholders
- Beauty-first — every pixel matters
Project Structure
src/
app/ # Next.js routes
components/ # React components
ui/ # shadcn/ui primitives
icons.tsx # Extracted SVG icons as React components
lib/
utils.ts # cn() utility (shadcn)
types/ # TypeScript interfaces
hooks/ # Custom React hooks
public/
images/ # Downloaded images from target site
videos/ # Downloaded videos from target site
seo/ # Favicons, OG images, webmanifest
docs/
research/ # Inspection output (design tokens, components, layout)
design-references/ # Screenshots and visual references
scripts/ # Asset download scripts
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 · 148 lines · 1,699 tokens per session scan A 87f295f765e4
webdev101 copilot-instructions.md is an instructions file published in the GitHub repository Smithaker10/webdev101 (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,699 tokens to every session, about $0.0085 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to ai-website-cloner-template copilot-instructions.md, differing in 6 lines, and is treated as a copy.
Other instructions, from other repositories
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.