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/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-proof-verify)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-proof-verify"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-proof-verify.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.00538 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
tell-proof-verify 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.
What it actually says
Tell Proof verify (agent workflow)
When you change rendered UI (components, styles, tokens, fixture pages), run proof verification before claiming done or opening a PR.
When to invoke
- After drafting a redesign patch with
tell_redesign/tell_apply - After editing
apps/weborfixtures/generic-appstyles that affect the captured surface - Before merge on any frontend PR that changes computed styles
MCP path (preferred in Cursor Agent)
1. tell_diagnose on the running preview URL (or localhost:3001 for fixture)
2. tell_redesign with direction
3. tell_apply with projectRoot set to the workspace
4. tell_proof_verify { url, patch, projectRoot }
5. If status is "failed" and reverted is true → revise patch and retry
6. If status is "passed" or "review" → human approves merge (never auto-merge)
Web / hosted path
- Local disposable checkout:
POST /api/proof/applywithjobId,patch,beforeReport - Hosted compare (Vercel preview):
POST /api/proof/verifywith{ mode: "compare", url, beforeReport, afterReport } - Hosted patch (capture backend):
POST /api/proof/verifywith{ url, patch, projectRoot }— proxied whenTELL_CAPTURE_API_URLis set
Verdict meanings
| Status | Meaning |
|---|---|
passed |
Score improved ≥3, screenshot changed, no focus/structure regression |
review |
Neutral or small change — human should judge |
failed |
Regression or patch did not apply — auto-reverted when configured |
Rules
- Never auto-merge on
passedalone — human reviews the diff - Always capture the same URL as the baseline report
- Prefer disposable checkout proof over editing the main branch directly
- After UI fixes, also run
pnpm dogfood:web(Tell must stay at zero tells)
Related
- Skill:
.cursor/skills/tell-proof-verify/SKILL.md - Skill:
.cursor/skills/tell-dogfood-audit/SKILL.md - Core:
packages/core/src/proof-verify.ts
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 · 54 lines · 0 tokens per session scan A 808babf26b1c
tell-proof-verify is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 538 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
11-testing-standards
General testing and validation standards.
test-engineer
Test Engineer agent.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.
playwright-api-testing-cursorrules-prompt-file
Cursor rules for Playwright development with API testing.
testing
Use when writing tests, deciding on test coverage, choosing between unit/integration/E2E tests, applying TDD, or reviewing test quality — covers rigor tiers, the Red-Green-Refactor cycle, coverage requirements, and Playwright for UI testing.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.