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-testinggit 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-testing)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-testing"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-testing.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 | $0.00000 | $0.00191 |
| Opus 5 | $0.00000 | $0.00096 |
| Sonnet 5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
tell-testing 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 3d 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
Testing rules
- Before claiming done, prefer
pnpm test,pnpm -F @tell/schema build, andpnpm -F @tell/web typecheck. - Root TypeScript is strict with
noUncheckedIndexedAccess; avoid unchecked array/object access. - Vitest includes
packages/**/*.test.ts; package tests should stay close to the package they verify. - Detector changes require golden assertions against
fixtures/reports/capture.json. - Taste tests must mock model calls and validate zod/reflection fallback behavior.
- UI changes should preserve keyboard access,
focus-visible, reduced motion, and non-color verdict encoding. - Known lower-coverage areas: redesign diffs, seam drag math, and the monolithic web page. Add focused tests when touching them.
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.
- 3d ago First seen · 16 lines · 0 tokens per session scan A 600f51ee3817
tell-testing is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 191 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
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.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.
react_hooks
React Hooks best practices for frontend package.