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-fixtures)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-fixtures"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-fixtures/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/rules/ashishpatill/tell-proof/tell-fixtures"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-fixtures.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.00000 | $0.00189 |
| Opus 5 | $0.00000 | $0.00095 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
tell-fixtures 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 10d 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
Fixture rules
fixtures/generic-appis demo input, not the Tell product; keep that attribution clear inCONTRIBUTIONS.md.- The fixture should intentionally trigger the planted genericness tells and drift findings from
BUILD.md. - If fixture UI changes, regenerate or update
fixtures/reports/capture.jsonandfixtures/reports/tell-report.jsontogether. - Detector expectations must move with fixture/report changes.
- Keep the fixture bland on purpose: Inter/system font, violet-pink gradient, repeated shadows/radii, emoji chrome, centered sections, gray mush.
- Preserve a brutalist or intentional case so taste can mark at least one finding
intentional. - The committed report is the offline demo fallback; do not break it while improving live capture.
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.
- 10d ago First seen · 16 lines · 0 tokens per session scan A 01f14c662201
tell-fixtures is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 189 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
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
tailwind-v4-core
Core Tailwind CSS v4 rules. Enforces correct v4 syntax and prevents common v3 fallbacks. Attach to all conversations involving Tailwind CSS.
tailwind-v4-migration
Tailwind CSS v3-to-v4 migration rules. Activated when the agent determines migration work is needed. Covers step-by-step upgrade process, common pitfalls, and automated migration tooling.
tailwind-v4-anti-patterns
Tailwind CSS v4 anti-pattern detection. Prevents the most common AI-generated mistakes: version mixing, deprecated config patterns, and removed utilities.
tailwind-v4-config
Tailwind CSS v4 configuration rules for CSS and build tool files. Covers @theme, @source, @import, PostCSS, and Vite plugin setup.
tailwind-v4-utilities
Tailwind CSS v4 utility class rules for template and markup files. Covers renamed classes, new utilities, container queries, gradients, and accessibility patterns.