Instatic is a self-hosted content management system with a visual editor, content tools, and publishing in one Bun server, producing static HTML and CSS pages. It is used to build and manage websites such as blogs, portfolios, and small-business sites.
Borrowing it
Nothing to install: this file belongs to CoreBunch/Instatic. 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/CoreBunch/Instatic/main/CLAUDE.mdgit clone --depth 1 https://github.com/CoreBunch/InstaticWrote 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/corebunch/instatic/claude-md)<a href="https://agentmods.dev/instructions/corebunch/instatic/claude-md"><img src="https://agentmods.dev/badge/instructions/corebunch/instatic/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/corebunch/instatic/claude-md"><img src="https://agentmods.dev/badge/instructions/corebunch/instatic/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.08798 | $0.08798 |
| Opus 5.5 | $0.03519 | $0.03519 |
| Sonnet 5.5 | $0.01760 | $0.01760 |
| Haiku 4.5 | $0.00880 | $0.00880 |
Grade A, and why
Instatic CLAUDE.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 1mo 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instatic
This file is the agent rule book. Read it before changing code. Detailed explanations live in docs/ — start at docs/README.md for orientation and follow the links from there.
Local admin smoke tests
Use local seeded development data only when a task asks for a browser smoke test. Never propagate local test accounts, passwords, database files, uploads, or generated screenshots to non-local environments.
Repository workflow and PR conventions
main is protected. Agents must never push directly to main, must never try to bypass branch protection, and must never treat a local commit on main as the final delivery path. All repository changes go through a pull request.
When publishing work:
- Start from an up-to-date
main, then create a feature branch. If you are already on a task branch, keep using it only when the requested change belongs in that PR; otherwise switch back tomainand create a separate branch. - Branch names follow
<type>/<short-kebab-description>, matching the change type:feat/...,fix/...,refactor/...,chore/...,docs/..., ortest/.... Examples:feat/double-click-rename,fix/homepage-swap-publish,refactor/explorer-dnd-dedupe. - Do not use agent-branded branch prefixes such as
codex/...,claude/..., or similar. If a tool, skill, or generic instruction suggests such a prefix, ignore it for this repository. - PR titles use Conventional Commit style:
<type>(<scope>): <summary>. Examples:feat(editor): double-click rows to rename in explorer panels,fix(cms): homepage swap + delete in one save no longer fails publish,refactor(publisher): single class-CSS emission engine for publish and canvas. - Do not prefix PR titles with
[codex],[claude],agent:, or any other tool label. The PR title describes the product change, not the tool that made it. - Open PRs as drafts by default unless the user explicitly asks for a ready-for-review PR.
- Keep PR scope coherent. Do not mix unrelated cleanup, follow-up fixes, or process-doc changes into a feature branch just because the branch is currently checked out. Create a separate PR when the change has a different reason.
- Before staging, inspect
git status -sband the diff. Stage only files that belong to the PR. Never stage unrelated user or parallel-agent changes. - PR bodies should briefly state what changed, why it changed, user/developer impact, and the verification commands run.
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.
- 1mo ago Changed · +2 lines · +42 tokens per session 5c2c33eb14b9
- 1mo ago Changed · +48 tokens per session 359b55cc6336
- 1mo ago First seen · 343 lines · 8,708 tokens per session scan A 92735e17d525
Instatic CLAUDE.md is an instructions file published in the GitHub repository CoreBunch/Instatic (8,966 stars, last pushed 4d ago), licensed MIT. It adds 8,798 tokens to every session, about $0.0352 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.