Borrowing it
Nothing to install: this file belongs to MaximeHeckel/blog.maximeheckel.com. 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/MaximeHeckel/blog.maximeheckel.com/main/AGENTS.mdgit clone --depth 1 https://github.com/MaximeHeckel/blog.maximeheckel.comWrote 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/maximeheckel/blog.maximeheckel.com/agents-md)<a href="https://agentmods.dev/instructions/maximeheckel/blog.maximeheckel.com/agents-md"><img src="https://agentmods.dev/badge/instructions/maximeheckel/blog.maximeheckel.com/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.01195 | $0.01195 |
| Opus 5 | $0.00598 | $0.00598 |
| Sonnet 5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
blog.maximeheckel.com 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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines
This document provides context for AI coding assistants working on this codebase.
Project Overview
A personal blog built with Next.js featuring interactive articles about web development, shaders, and 3D graphics. The blog emphasizes rich interactive experiences through custom MDX widgets, WebGL visualizations, and code playgrounds.
Live site: https://blog.maximeheckel.com
Tech Stack
| Category | Technology |
|---|---|
| Framework | Next.js 15 (Pages Router) |
| UI | React 19, @maximeheckel/design-system |
| Headless UI | @base-ui/react (Select, Dialog, etc.) |
| Styling | Stitches (via design-system), CSS custom properties |
| Animation | Motion library (framer-motion successor) |
| 3D/WebGL | Three.js, @react-three/fiber, @react-three/drei, postprocessing |
| Content | MDX with next-mdx-remote |
| Testing | Vitest + Testing Library, Cypress for E2E |
| Package Manager | pnpm |
Directory Structure
├── core/
│ ├── components/ # Reusable UI components
│ ├── features/ # Feature-specific components (BlogPost, IndexSection)
│ └── hooks/ # Custom React hooks
├── pages/ # Next.js pages (NOT app router)
├── content/ # MDX blog posts
├── lib/ # Utilities, config, rehype plugins
├── types/ # TypeScript type definitions
├── scripts/ # Build scripts (RSS, sitemap, OG images)
├── cypress/ # E2E tests
└── public/ # Static assets
Detailed Rules
Tool-neutral, context-specific coding guidelines are located in docs/agent-guidelines/. These Markdown files are the canonical source for every coding agent.
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.
- 8d ago First seen · 102 lines · 1,195 tokens per session scan A 28f12bde2ae6
blog.maximeheckel.com AGENTS.md is an instructions file published in the GitHub repository MaximeHeckel/blog.maximeheckel.com (735 stars, last pushed 8d ago), licensed MIT. It adds 1,195 tokens to every session, about $0.0060 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.