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.
git clone --depth 1 https://github.com/florianwittkamp/bring-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/rules/florianwittkamp/bring-mcp/bring-mcp-guidelines)<a href="https://agentmods.dev/rules/florianwittkamp/bring-mcp/bring-mcp-guidelines"><img src="https://agentmods.dev/badge/rules/florianwittkamp/bring-mcp/bring-mcp-guidelines.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.03085 | $0.03085 |
| Opus 5 | $0.01543 | $0.01543 |
| Sonnet 5 | $0.00617 | $0.00617 |
| Haiku 4.5 | $0.00309 | $0.00309 |
Grade A, and why
bring-mcp-guidelines 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 8d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bring! MCP Server Project Guidelines
This document outlines key conventions, structures, and important points for working with the bring-mcp TypeScript project.
Project Overview
- Purpose: Implements a Model Context Protocol (MCP) server that exposes the Bring! shopping list API.
- Language: TypeScript
- Key Libraries:
@modelcontextprotocol/sdk: For MCP server implementation.@modelcontextprotocol/inspector: For testing and debugging MCP servers.bring-shopping: Node.js wrapper for the Bring! API.zod: For schema definition and validation.dotenv: For managing environment variables.jest: For testing.eslint&prettier: For linting and formatting.
Directory Structure
.cursor/rules/: Contains Cursor AI project-specific rules like this one.src/: Main application source code.index.ts: Entry point, MCP server setup,registerToolhelper function, and themainfunction which initializesBringClientand registers tools.bringClient.ts: A wrapper class around thebring-shoppinglibrary, centralizing all interactions with the Bring! API.schemaShared.ts: Defines common Zod schema parts (e.g.,listUuidParam,itemIdParam,itemNameParam,itemSpecificationParam,itemImagePathOrUrlParam,batchItemSchema,saveItemBatchParams,itemNamesArrayParam) for reuse across tool schemas.tools/: Contains modularized tool registration functions.listTools.tsitemTools.ts: Includes tools likesaveItem,saveItemBatch,deleteMultipleItemsFromList.userTools.ts: Includes tools likegetAllUsersFromList,getUserSettings,getPendingInvitations, andgetDefaultList.catalogTools.ts
tests/: Contains Jest test files (e.g.,*.spec.ts)..env: Used for storing Bring! API credentials (MAIL,PW). This file should not be committed to version control.assets/: Contains static assets like images for the README.eslint.config.js: ESLint configuration.jest.config.js: Jest test runner configuration.tsconfig.json: TypeScript compiler configuration.package.json: Project metadata, dependencies, and npm scripts.
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.
- 8d ago First seen · 184 lines · 3,085 tokens per session scan A b4cf5d851683
bring-mcp-guidelines is a cursor rule published in the GitHub repository florianwittkamp/bring-mcp (27 stars, last pushed 2d ago), licensed MIT. It adds 3,085 tokens to every session, about $0.0154 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-30.
Other cursor rules, from other repositories
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
toc-readme
When updating README.md, the table of contents should contain only the second-level headings below it.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
php-client-implementation
Guidelines for implementing MCP clients in PHP.
cursor_rules
Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.
validate-design-early
Ask for design approval before implementing 100+ lines.