Borrowing it
Nothing to install: this file belongs to pedramamini/WisprMCP. 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/pedramamini/WisprMCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/pedramamini/WisprMCPWrote 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/pedramamini/wisprmcp/claude-md)<a href="https://agentmods.dev/instructions/pedramamini/wisprmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pedramamini/wisprmcp/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.01265 | $0.01265 |
| Opus 5 | $0.00633 | $0.00633 |
| Sonnet 5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
WisprMCP 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Development Guide for WisprMCP
This document provides guidance for Claude Code when working with the WisprMCP project.
Project Overview
WisprMCP is a Python library that provides access to Wispr Flow's SQLite database. It includes:
- Core Library (
wispr_mcp/core/): Database access and data models - CLI Tools (
wispr_mcp/cli/): Command-line interface with 6 commands - MCP Server (
wispr_mcp/mcp/): JSON-RPC 2.0 server for AI integration - Utilities (
wispr_mcp/utils/): Configuration and date parsing
Development Practices
Code Style
- Follow PEP 8 style guidelines
- Use type hints where possible
- Keep functions focused and well-documented
- Zero external dependencies policy
Testing
- Run tests with:
pytest - Test coverage with:
pytest --cov=wispr_mcp - Test specific files:
pytest tests/test_parser.py
Formatting
- Format code with:
black wispr_mcp/ - Check style with:
flake8 wispr_mcp/ - Type checking with:
mypy wispr_mcp/
Common Commands
Installation
pip install -e . # Install in development mode
pip install -e ".[dev]" # Install with dev dependencies
CLI Testing
wispr list # List recent transcripts
wispr search "test" # Search functionality
wispr stats # Database statistics
wispr --help # Show help
MCP Server Testing
python wispr_mcp/mcp/server.py --debug # Run MCP server in debug mode
Architecture Notes
Database Access
- Uses SQLite3 from Python standard library
- Read-only access to Wispr Flow database
- Context manager pattern for connection handling
- Graceful error handling for missing/corrupted data
Data Models
TranscriptEntry: Individual transcript with metadataConversation: Grouped transcript entriesTranscript: Collection of entries with statistics
CLI Design
- Argparse-based command structure
- Colored output with ANSI escape codes
- Multiple output formats (table, JSON, text, markdown)
- Consistent error handling and user feedback
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 · 172 lines · 1,265 tokens per session scan A 3f789de9ee3d
WisprMCP CLAUDE.md is an instructions file published in the GitHub repository pedramamini/WisprMCP (5 stars, last pushed 1y ago), licensed MIT. It adds 1,265 tokens to every session, about $0.0063 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
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 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).
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.
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.