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/jdevalk/cocktail.glass/claude-mdgit clone --depth 1 https://github.com/jdevalk/cocktail.glassWrote 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/jdevalk/cocktail.glass/claude-md)<a href="https://agentmods.dev/instructions/jdevalk/cocktail.glass/claude-md"><img src="https://agentmods.dev/badge/instructions/jdevalk/cocktail.glass/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 | $0.00918 | $0.00918 |
| Opus 5 | $0.00459 | $0.00459 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
cocktail.glass 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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cocktail.glass
Stack
- Astro 6 static site, deployed to Cloudflare Pages
- No JS framework — vanilla inline scripts with
is:inline. One exception:src/components/WebMcp.astrois a bundled module (nois:inline) because itimports the sharedcocktail-tools.mjstool module, and inline scripts cannot import. - Pagefind for search (custom UI, not PagefindUI)
cocktail-tools.mjs(repo root) holds the seven MCP tool definitions and matching logic. Both the remote MCP server (functions/mcp.js) and the in-browser WebMCP integration import it — change a tool in one place.
HTML principles
- Minimize attributes per element. Avoid adding classes when the element can be targeted by its position in the DOM (e.g.,
.grid > a > h3instead of.card-nameon every card). - Don't add
data-attributes that duplicate information derivable from the DOM tree (e.g., don't putdata-categoryon every card when the parent section already has it). - Use
is:globalstyles instead of Astro's scoped styles for pages with many repeated elements — scoped styles add adata-astro-cid-*attribute to every element, which adds significant weight at scale (saved ~155KB on the homepage with 500 cards). - Scope bare element selectors (e.g.,
header,h1) to a parent class when usingis:globalto prevent them bleeding into the layout.
CSS principles
- Prefer cascading selectors over class-per-element. Inside a known structure like
.grid > a, target children by element type and position rather than adding classes. - When converting from scoped to global styles, remove
:global()wrappers — they create broken double-global selectors inside<style is:global>. - Use
scroll-margin-topon anchor targets to account for the sticky header.
Performance
- Only the first 4 images in the homepage grid are eager-loaded (
loading="eager",fetchpriority="high"). The first image is also preloaded via<link rel="preload">. - JSON-LD schema and search overlay JS are in the footer, after visible content.
- System font stack for body text (
--font-sans), custom font only for display headings (Playfair Display). Only the latin subset is loaded. - Homepage is ~526KB raw / ~54KB gzipped with 500 cocktail cards.
- Use
content-visibility: autoon category sections for render performance.
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.
- 4d ago First seen · 49 lines · 918 tokens per session scan A e89a694a9e52
cocktail.glass CLAUDE.md is an instructions file published in the GitHub repository jdevalk/cocktail.glass (7 stars, last pushed 10d ago), licensed MIT. It adds 918 tokens to every session, about $0.0046 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
specification.website CLAUDE.md
Claude Code instructions for jdevalk/specification.website, covering what this project is, status discipline, changelog, cardinal rules for content and architecture quick reference.
seo-graph AGENTS.md
Instructions for jdevalk/seo-graph, covering agents.md — seo-graph, what this library does, architecture, installation and astro projects — install both.
seo-graph copilot-instructions.md
Instructions for jdevalk/seo-graph: Read AGENTS.md in the repository root for the complete API reference, site type recipes, and integration guide. It covers every piece builder, every common site type, and how to wire entities together.
AnvilWiki AGENTS.md
AGENTS.md instructions for PNGTRID/AnvilWiki, covering agents.md, repository purpose, read these first, intended tech stack (verified, as of 2026-08-11) and architecture: code/config/content separation (critical).
seo-graph CLAUDE.md
Instructions for jdevalk/seo-graph: Read AGENTS.md for the complete API reference, site type recipes, and integration guide. It covers every piece builder, every common site type, and how to wire entities together.
ui.plan.ai AGENTS.md
AGENTS.md instructions for planailabs/ui.plan.ai, covering agent guide, toolchain, layout, commands and skills.