Borrowing it
Nothing to install: this file belongs to shoot-here/moltamp-skins. 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/shoot-here/moltamp-skins/main/CLAUDE.mdgit clone --depth 1 https://github.com/shoot-here/moltamp-skinsWrote 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/shoot-here/moltamp-skins/claude-md)<a href="https://agentmods.dev/instructions/shoot-here/moltamp-skins/claude-md"><img src="https://agentmods.dev/badge/instructions/shoot-here/moltamp-skins/claude-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.01485 | $0.01485 |
| Opus 5 | $0.00743 | $0.00743 |
| Sonnet 5 | $0.00297 | $0.00297 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
moltamp-skins 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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MOLTamp Skins -- AI Contributor Guide
Community skin repository for MOLTamp. Skins are pure CSS themes -- no JavaScript.
Repository Structure
moltamp-skins/
├── skins/ <- Each subfolder is a complete skin
│ └── <skin-id>/
│ ├── skin.json <- Manifest (required)
│ ├── theme.css <- All styles (required, 100KB max)
│ └── assets/ <- Images, GIFs, fonts (optional)
├── screenshots/ <- Skin preview images
├── SKINNING.md <- Full specification (read this first)
├── CONTRIBUTING.md <- PR guidelines
└── README.md <- Overview + skin catalog
Critical Rules -- NEVER Violate These
- All colors as CSS variables in
:root. Never hardcode hex/rgb in selectors. - Contract variables are the API.
--t-*(terminal),--c-chrome-*(chrome),--effect-*(effects). - No backgrounds on
.moltamp-vibes. Vibes art usesskin.jsonGIF slots. - Every
::before/::afterneedspointer-events: none. Always. - Every animation/glow/filter must be gated with
--effect-*variables. No ungated effects. - No external URLs, no
@import, nojavascript:, noexpression(). CSS only, zero network. - No targeting Moltamp internal UI. Hard block -- skin won't load. Stick to the documented
.moltamp-*classes. - Custom variables use
--skin-*prefix. E.g.,--skin-panel-bg,--skin-overlay. - Never use
*(universal selector) with display, opacity, pointer-events, or position. - Never set
overflow: hiddenon.moltamp-shell,.moltamp-deck,.moltamp-titlebar, or.moltamp-statusbar. - Don't reference reserved internal chrome variable namespaces. Several
--*namespaces are reserved for Moltamp's internal UI and are hard-blocked by the validator. Keep all custom variables under the documented--skin-*,--t-*,--c-*, or--effect-*prefixes. You'll see a clear error on import if you stray. - Don't try to hide forbidden tokens behind CSS escapes. The validator normalizes escape sequences (both hex
\6eand identity\nforms) before pattern matching, so escape tricks will still be caught. Write CSS normally.
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.
- 7d ago First seen · 111 lines · 1,485 tokens per session scan A e0caedca872f
moltamp-skins CLAUDE.md is an instructions file published in the GitHub repository shoot-here/moltamp-skins (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,485 tokens to every session, about $0.0074 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-31.
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.
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.
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).
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.