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/vinta/laughing-man/claude-mdgit clone --depth 1 https://github.com/vinta/laughing-manWrote 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/vinta/laughing-man/claude-md)<a href="https://agentmods.dev/instructions/vinta/laughing-man/claude-md"><img src="https://agentmods.dev/badge/instructions/vinta/laughing-man/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.01035 | $0.01035 |
| Opus 5 | $0.00517 | $0.00517 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
laughing-man 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 6d 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.
This is a copy
97% identical to laughing-man AGENTS.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
laughing-man is a CLI tool that turns a folder of Markdown files into a newsletter: a static archive site on Cloudflare Pages and email delivery via Resend Broadcasts. Built with Bun + TypeScript.
Commands
laughing-man init # Generate laughing-man.yaml
laughing-man setup web # Create Cloudflare Pages project + custom domain + DNS
laughing-man setup newsletter # Verify Resend API key + sender domain + DNS records
laughing-man build # Validate + generate site + email HTML (excludes drafts)
laughing-man preview # Build (including drafts) + local server with live reload
laughing-man stamp # Add frontmatter to .md files that don't have it
laughing-man deploy # Deploy to Cloudflare Pages via wrangler
laughing-man send <N> # Send issue N via Resend Broadcast
laughing-man send status # Show delivery status for all sent broadcasts
Install from npm: npm install -g laughing-man-cli
Or run without installing: npx laughing-man-cli <command>
Tech Stack
- Runtime: Node.js 22+ (published package). Bun for development/testing.
- Language: TypeScript (strict mode)
- Templates: Plain TypeScript functions returning HTML strings (no React, no JSX)
- Email: MJML for responsive email HTML
Development
bun test # Run tests
bun run typecheck # TypeScript check
bun run build # Compile TS + copy assets to dist/
bun src/cli.ts --help # Run CLI locally
A PostToolUse hook auto-runs bun run build when source files are edited. If the hook is not active, run it manually after code changes to keep dist/ in sync.
Local CLI Testing
Run bun link from the project root to register the package globally. This symlinks to source, so code changes take effect immediately without re-running.
bun link # One-time setup
laughing-man --help # Works from any directory
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.
- 6d ago First seen · 101 lines · 1,035 tokens per session scan A 065b87d371ee
laughing-man CLAUDE.md is an instructions file published in the GitHub repository vinta/laughing-man (11 stars, last pushed 1mo ago), licensed MIT. It adds 1,035 tokens to every session, about $0.0052 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to laughing-man AGENTS.md, differing in 4 lines, and is treated as a copy.
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).
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.
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 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.