Borrowing it
Nothing to install: this file belongs to jej2k5/meetey. 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/jej2k5/meetey/main/CLAUDE.mdgit clone --depth 1 https://github.com/jej2k5/meeteyWrote 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/jej2k5/meetey/claude-md)<a href="https://agentmods.dev/instructions/jej2k5/meetey/claude-md"><img src="https://agentmods.dev/badge/instructions/jej2k5/meetey/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.09015 | $0.09015 |
| Opus 5 | $0.04508 | $0.04508 |
| Sonnet 5 | $0.01803 | $0.01803 |
| Haiku 4.5 | $0.00902 | $0.00902 |
Grade A, and why
meetey 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 — 564 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project
Meetey is a local-first meeting capture and summarization tool that runs entirely within Claude Code. It captures audio from running meeting apps (Google Meet, Zoom, Microsoft Teams) using macOS ScreenCaptureKit, transcribes locally with whisper.cpp, and produces structured summaries via Claude. Optionally it also captures screen keyframes with on-device OCR.
Recording, transcription, and OCR are all local; no third-party meeting service is involved. The summary itself is written by Claude, so transcript and OCR text does go to the API — keep that distinction accurate in docs and user-facing copy.
Setup
npx jej2k5/meetey install
This builds the Swift binary, downloads the Whisper model, copies the MCP server and skill to ~/.meetey/, registers the MCP server in ~/.claude.json, and adds Claude Code shortcuts.
Commands
| Command | Purpose |
|---|---|
npx jej2k5/meetey install |
First-time setup (or node cli/index.js install from a local clone) |
npx jej2k5/meetey update |
Rebuild binary, refresh MCP server and skill |
npx jej2k5/meetey status |
Show what's installed and whether everything is wired up |
npx jej2k5/meetey watch enable|disable|status|logs |
Control the meeting watcher (also /meetey watch from Claude Code) |
swift build -c release |
Rebuild the Swift capture binary (run inside meetey-capture/) |
.build/release/meetey-capture --selftest |
Keyframe pipeline + auto-stop, no permission needed |
node daemon/watch.js --selftest |
Meeting-detection patterns |
node mcp-server/index.js |
Run the MCP server manually for debugging |
codesign --force --sign - --options runtime --entitlements entitlements.plist .build/release/meetey-capture |
Re-sign after a Swift rebuild (run inside meetey-capture/) |
Architecture
User → /meetey (skill) → MCP server (Node.js) → meetey-capture (Swift CLI)
→ whisper-cli
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 · 564 lines · 9,015 tokens per session scan A 02b4b60a9a22
meetey CLAUDE.md is an instructions file published in the GitHub repository jej2k5/meetey (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 9,015 tokens to every session, about $0.0451 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.