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-demo-narrative)<a href="https://agentmods.dev/rules/ashishpatill/tell-proof/tell-demo-narrative"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-demo-narrative/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-demo-narrative"><img src="https://agentmods.dev/badge/rules/ashishpatill/tell-proof/tell-demo-narrative.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.00196 |
| Opus 5 | $0.00000 | $0.00098 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
tell-demo-narrative 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
Demo and compliance rules
- Lead with Ashish's journey: capture → named tells → seam → voice → draft fix → Apply in Cursor.
- The product is the loop, not a KPI dashboard — avoid disqualifying "dashboard as main feature" framing.
- Demo only what the team built in-event;
CONTRIBUTIONS.mdseparates work fromfixtures/generic-app. - Generic fixture is demo input, not original contribution — label it clearly.
- Backup plan: committed
fixtures/reports/tell-report.jsonwhen live capture or API keys fail. - Close with dogfood: "Tell runs on itself: zero tells."
- Copy uses critic voice from
USER_STORY.md; no emoji chrome in product UI.
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 7eeedc77bb21
tell-demo-narrative is a cursor rule published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 196 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
graphql-apollo-client-usage
A usage guide for fetching, changing, and subscribing to GraphQL data with Apollo Client in React. It covers loading and error states, cache updates, refetching, and reusable GraphQL fragments.
graphql-typescript-integration
A TypeScript rule for GraphQL operations that uses the API schema and queries to generate types. It helps type-check data and variables from the GraphQL server through to React components.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
observer-hoc-or-useobserver-hook
Guidance for making React components respond to changes in MobX observable data by wrapping them with an observer or using the useObserver Hook.
react-functional-components-preference
A React style rule that prefers function components with Hooks such as useState and useEffect over class components. Hooks are React functions for managing state and other component behavior.
chakra-ui---component-composition
A React component-structure rule for composing Chakra UI components into reusable interfaces. It favors small custom components built from layout and interface pieces such as Box, Flex, and Stack.