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/davebream/bullet-mcp/claude-mdgit clone --depth 1 https://github.com/davebream/bullet-mcpWrote 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/davebream/bullet-mcp/claude-md)<a href="https://agentmods.dev/instructions/davebream/bullet-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/davebream/bullet-mcp/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.00944 | $0.00944 |
| Opus 5 | $0.00472 | $0.00472 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
bullet-mcp 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 — 83 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.
What This Is
An MCP (Model Context Protocol) server wrapping the Bullet API — a task/note/event manager with collections and tags. The MCP server version is kept 1:1 with the API version defined in spec/openapi.json.
Commands
bun install # Install dependencies
bun run build # Compile TypeScript → dist/
bun run test # Run all tests (vitest)
bun run test:watch # Run tests in watch mode
bun run typecheck # Type-check without emitting
bun run lint # Biome lint + format check
bun run lint:fix # Auto-fix lint/format issues
bun run generate # Regenerate types from OpenAPI spec
Run a single test file: bunx vitest run tests/client/api.test.ts
Run tests matching a name: bunx vitest run -t "listEntries"
Architecture
Spec-First, TDD Workflow
spec/openapi.json— single source of truth for the Bullet API contractbun run generate→src/client/types.generated.ts(auto-generated, never hand-edit)src/client/types.ts— ergonomic re-exports from the generated types- Tests are written before implementation; tests in
tests/server/registration.test.tsverify that MCP tool definitions stay aligned with the OpenAPI spec (enums, required fields, parameter names)
Functional Core / Imperative Shell
- Pure tool handlers (
src/tools/entries.ts,collections.ts,tags.ts):(client, params) → string. No MCP awareness, no I/O beyond the injected client. Trivially testable with stub clients. - Formatting (
src/tools/format.ts): Pure functions that render domain objects to text. - Zod schemas (
src/tools/definitions.ts): Define MCP tool input schemas with Zod, mirroring the OpenAPI spec. Also exportsTOOL_DEFINITIONS(JSON Schema form) used by registration tests. - Server shell (
src/index.ts): Wires Zod schemas + handlers intoMcpServer.registerTool(). ReadsBULLET_API_TOKENfrom env. This is the only file with side effects.
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 · 83 lines · 944 tokens per session scan A 493a032c251b
bullet-mcp CLAUDE.md is an instructions file published in the GitHub repository davebream/bullet-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 944 tokens to every session, about $0.0047 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).
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.
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).