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-domain-research)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-domain-research"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-domain-research/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-domain-research"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-domain-research.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.00324 | $0.00324 |
| Opus 5.5 | $0.00130 | $0.00130 |
| Sonnet 5.5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
tell-domain-research 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 2mo 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
Domain research — auto-trigger
Before designing, coding, or running agency:run / designFromFeatures for any new or redesigned website:
- Auto-run
website-domain-research(LoadPriorDomain → requirement-gap-diff → walkthrough if gaps → IA → variant-lens → emit-training-episode). - If the brief is cricket / football / hockey / tennis / live scores / matchday, also auto-run
sport-matchday-web/sport-site-research(extends the general graph). - Do not blank-slate when a
DomainResearchPackexists — customize or gap-fill only. - Engine already prepends
website-domain-researchinrouteSkills/designFromFeatures; agents must still execute the research nodes (not only render craft). - After research, execute every craft node
routeSkillsreturns (including always-onresponsive-performance) — do not wait for the user to wire skills. - After photography lands under
apps/web/public/**, auto-runpnpm media:siteand useSiteImg(seetell-site-build-autoload).
Skills: .cursor/skills/website-domain-research, .cursor/skills/sport-matchday-web, .cursor/skills/sport-site-research, .cursor/skills/responsive-performance, child nodes load-prior-domain … emit-training-episode.
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.
- 2mo ago First seen · 18 lines · 324 tokens per session scan A aa0fe5b5dfe8
tell-domain-research is a cursor rule published in the GitHub repository ashishpatill/tell-proof (2 stars, last pushed 26d ago), licensed MIT. It adds 324 tokens to every session, about $0.0013 per session on Opus 5.5. 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
orchestrate
Orchestrate challenge playbook. Start here for any HackerRank Orchestrate work.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.
lean
Answer densely. Cut filler, keep all technical signal.
secure-dev-rust
These rules apply to all Rust code in the repository and aim to prevent common security risks through disciplined use of memory safety, input validation, error handling, and safe APIs.