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 rules/ashishpatill/tell-proof/tell-mcp-apigit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/tell-mcp-api)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-mcp-api"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-mcp-api.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.00000 | $0.00289 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
tell-mcp-api 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 5d 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.
What it actually says
MCP and API rules
tell_capture,tell_diagnose,tell_redesign,tell_apply, matrix/proof/design/voice/install_info are the public Cursor surface.- Tool names are gated by
@tell/schemaMCP_TOOL_NAMES— keep skill docs andREGISTERED_MCP_TOOLSin sync. tell_applyreturns patch text and instructions only. It must never write to the user's repo.- Web
/api/diagnosemay use deterministic subprocess output; MCPtell_diagnosemay add taste when keys exist. GET /api/install-infoandtell mcp install cursorare the Connect Agent source of truth.- When
TELL_CAPTURE_API_TOKENis set, diagnose requires Bearer /x-tell-capture-token. - All API failures should return plain-language state and preserve the offline report fallback.
/api/setup/*andrepo-runner.tsexecute cloned repo scripts and are local-dev only.- Keep
.cursor/mcp.jsonregistered aspnpm -F @tell/mcp startunless the package script changes.
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.
- 5d ago First seen · 18 lines · 0 tokens per session scan A 011b608555e1
tell-mcp-api is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 289 tokens. 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 cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
lean
Answer densely. Cut filler, keep all technical signal.