Borrowing it
Nothing to install: this file belongs to ashishpatill/tell-proof. 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/ashishpatill/tell-proof/master/.cursor/skills/tell-mcp-tools/SKILL.mdgit 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/skills/ashishpatill/tell-proof/tell-mcp-tools)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/tell-mcp-tools"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-mcp-tools/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/tell-mcp-tools"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-mcp-tools.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00858 |
| Opus 5 | $0.00022 | $0.00429 |
| Sonnet 5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
tell-mcp-tools scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s localhost:3000/api/install-info | jq .platforms How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tell MCP tools
Scope
packages/mcp/src/index.ts— stdio MCP serverpackages/schema—McpToolName/InstallInfo/buildInstallInfo.cursor/mcp.json— registerspnpm -F @tell/mcp startGET /api/install-info+tell mcp install <platform>— Connect Agent / platform catalog
Tools
| Tool | Args | Returns |
|---|---|---|
tell_capture |
{ url } |
CapturePayload |
tell_diagnose |
{ url?, reportPath? } |
TellReport (with id) |
tell_redesign |
{ direction, findingId?, reportId? } |
RedesignProposal |
tell_apply |
{ proposalId?, projectRoot? } |
{ patches, instruction } |
tell_capture_matrix |
{ url, routes?, compare? } |
matrix + proof |
tell_proof_verify |
{ url, patch, projectRoot?, … } |
proof verdict |
tell_proof_revert |
{ projectRoot?, patch? } |
{ reverted } |
tell_design_from_features |
brief fields | DesignSpec (+ HTML) |
tell_voice |
{ transcript } |
direction plan + source |
tell_install_info |
{ launch? } |
InstallInfo |
tell_resolve_intent |
{ text, fixtureUrl? } |
ResolvedIntent |
Web-only today: /api/setup/*, share links (see docs/11).
Rules
- Parse all inputs/outputs with
@tell/schema tell_applyreturns patch text only — never writes filestell_diagnosewithout URL/report falls back tofixtures/reports/tell-report.json- Tool names must match
MCP_TOOL_NAMES(vitest drift guard) - MCP and web API share the same engine contracts
- When sibling
tell-design-dataexists,tell_diagnose/tell_redesign/tell_proof_verify/tell_design_from_featureswrite raw episodes via the same sink as/api/design(@tell/design-skills/training-data-sink). Missing sink ⇒ no-op. Still eleven tools; no public MCP host.
One-click / install
tell mcp install cursor --project # upsert .cursor/mcp.json
tell mcp install claude # claude mcp add-json or .mcp.json
tell mcp install opencode --project
tell mcp install grok --project
tell mcp platforms # compatibility table
tell mcp print-config # all agent snippets + deeplink
curl -s localhost:3000/api/install-info | jq .platforms
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 · 85 lines · 44 tokens per session scan A 4863ada3dc1d
tell-mcp-tools is a skill published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 858 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
better-design
Build, improve, and review production interfaces with the Better Design MCP. Use for frontend design, UI, UX, interactions, flows, forms, navigation, components, styling, design systems, accessibility, responsive layouts, motion, React Native, Expo, Shopify, Three.js, and product video work, especially when creating…
Add Claude design-system and accessibility workflows with UX/UI Agent Skills
Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.
design-maker
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…
design-brief-builder
name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…