Borrowing it
Nothing to install: this file belongs to jonradoff/lightcms. 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/jonradoff/lightcms/main/CLAUDE.mdgit clone --depth 1 https://github.com/jonradoff/lightcmsWrote 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/jonradoff/lightcms/claude-md)<a href="https://agentmods.dev/instructions/jonradoff/lightcms/claude-md"><img src="https://agentmods.dev/badge/instructions/jonradoff/lightcms/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/jonradoff/lightcms/claude-md"><img src="https://agentmods.dev/badge/instructions/jonradoff/lightcms/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.10086 | $0.10086 |
| Opus 5.5 | $0.04034 | $0.04034 |
| Sonnet 5.5 | $0.02017 | $0.02017 |
| Haiku 4.5 | $0.01009 | $0.01009 |
Grade A, and why
lightcms 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 20d 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 — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read VIBECTL.md for current project status, deployment details, and issue context before starting work.
LightCMS - Claude Code Memory
Project Overview
LightCMS is a lightweight, self-hosted content management system built in Go. It uses MongoDB for data storage and generates static HTML pages for public content serving.
Key URLs:
- Admin Dashboard:
/cm - Public Site:
/ - MCP Server:
bin/lightcms-mcp(stdio transport)
MCP Server Integration
IMPORTANT: All website content operations MUST go through the MCP server. Do NOT:
- Write scripts to directly modify the database
- Use Go code to create/edit/delete content
- Bypass the MCP server for any content management tasks
If the MCP server is not available or not working, ASK the user for permission before attempting any content changes through other means.
Starting the MCP Server
If the user requests a content operation and the MCP server is not yet running, start it using the convenience script:
./bin/lightcms-mcp-wrapper.sh
This wrapper script sets up the required environment variables (LIGHTCMS_CONFIG_DIR) and launches the MCP server. The MCP server uses stdio transport, so it will be connected automatically once started.
Content Operations (REQUIRE MCP or explicit user permission):
- Creating, editing, publishing, or deleting content
- Managing templates and their HTML layouts
- Uploading or managing assets (images, CSS, JS, documents)
- Updating theme settings (colors, fonts, header/footer HTML)
- Managing redirects, folders, and collections
- Viewing or reverting content versions
- Site configuration changes
Code Changes (allowed without MCP):
- Adding new features to LightCMS itself
- Fixing bugs in the application
- Changing application behavior or logic
- Adding new MCP tools
- Modifying database schemas or indexes
- Security improvements
⚠️ IMPORTANT: Rebuild MCP binary after adding tools
The Claude Desktop MCP integration uses a local binary (bin/lightcms-mcp) that connects to the remote server. The binary encodes all tool definitions — if you add or remove MCP tools without rebuilding it, Claude Desktop will see stale/missing 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.
- 20d ago Changed · +13 lines · +1,437 tokens per session d6c2776450d9
- 22d ago Changed · +20 lines · +1,926 tokens per session 1072d736051f
- 24d ago Changed · +6 tokens per session f83e284c7ff9
- 26d ago Changed · +11 lines · +403 tokens per session fad7aaab777c
- 28d ago Changed · +7 lines · +199 tokens per session 242757cb9eb6
- 2mo ago First seen · 491 lines · 6,115 tokens per session scan A a02060b9f3d2
lightcms CLAUDE.md is an instructions file published in the GitHub repository jonradoff/lightcms (32 stars, last pushed 21d ago), licensed MIT. It adds 10,086 tokens to every session, about $0.0403 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.