tell-proof: Agent for Claude Code

.cursor/agents/demo-director.md

demo-director is an agent for Claude Code, Cursor from ashishpatill/tell-proof. It costs 52 tokens per session (410 once invoked), scanned A, original, MIT.

A demo-planning agent for Tell that prepares and checks a three-minute product demonstration against the project’s story, rules, attribution requirements, and backup materials.

In plain words
What is it for?
Use it to rehearse the demo, verify its five story beats, check event-work and open-source requirements, and report readiness, blockers, fallback materials, and opening and closing lines.
Why use it?
It helps catch missing demo states, stale data, failed microphone handling, compliance issues, and unavailable fallbacks before a review.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is ashishpatill/tell-proof's own configuration. It tells Claude Code and Cursor how to work on tell-proof itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tell-proof configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ashishpatill/tell-proof. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ashishpatill/tell-proof/master/.cursor/agents/demo-director.md
Clone the repo
git clone --depth 1 https://github.com/ashishpatill/tell-proof

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for demo-director

README.md
[![agentmods](https://agentmods.dev/badge/agents/ashishpatill/tell-proof/demo-director/github.svg)](https://agentmods.dev/agents/ashishpatill/tell-proof/demo-director)
Your own site
<a href="https://agentmods.dev/agents/ashishpatill/tell-proof/demo-director"><img src="https://agentmods.dev/badge/agents/ashishpatill/tell-proof/demo-director/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.

agentmods 80×15 button for demo-director

Your own site · 80×15
<a href="https://agentmods.dev/agents/ashishpatill/tell-proof/demo-director"><img src="https://agentmods.dev/badge/agents/ashishpatill/tell-proof/demo-director.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 410 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00410
Opus 5 $0.00026 $0.00205
Sonnet 5 $0.00010 $0.00082
Haiku 4.5 $0.00005 $0.00041

Measured 9d ago against content hash 90a70ce714a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

demo-director 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 9d 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.

.cursor/agents/demo-director.md · 55 lines

What it actually says

You are Tell's demo director. You make viewers feel Ashish's problem in 3 minutes.

Authority

  • USER_STORY.md — persona and journey beats
  • docs/04_CLAUDE_PROJECT.md §15–16 — demo script and compliance
  • CONTRIBUTIONS.md — original work vs demo input

5-beat script

  1. Setup — paste repo/URL
  2. Capture + diagnose — score line + named tells
  3. Taste — generic tell + intentional finding
  4. Before/after — seam drag with contrast callout
  5. Voice + reconcile — direction change → draft fix → Apply in Cursor

Compliance checklist

  • Repo public and open source
  • Demo shows only in-event work
  • Fixture clearly labeled demo input
  • Not framed as a dashboard product
  • Dogfood close: zero tells on Tell itself

Fallback plan

  1. Committed fixtures/reports/tell-report.json
  2. Seeded fixture on :3001
  3. Recorded backup video

Hardening tasks

  • Empty/loading/error states in plain language
  • Hide stale capture during setup
  • Offline badge when meta.live: false
  • Voice text presets when mic fails

Output

Demo readiness: [ready | at-risk]
Blockers: [list]
Fallback: [artifact | fixture | video]
Opening line: [one sentence for viewers]
Close line: [dogfood + Apply in Cursor]

Delegate UI fixes to ui-builder; copy to ux-copywriter; deploy URL to deploy-engineer.

Changes

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.

  1. 9d ago First seen · 55 lines · 52 tokens per session scan A 90a70ce714a1

Subscribe to this mod's changes

demo-director is an agent published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 14d ago), licensed MIT. It adds 52 tokens to every session and 410 once invoked, about $0.0003 per session on Opus 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.

Related

Other agents, from other repositories

ring:ui-engineer

UI Implementation Engineer specialized in translating product-designer outputs (ux-criteria.md, user-flows.md, wireframes/) into production-ready React/Next.js components with Design System compliance and accessibility standards.

LerianStudio/ring · 46 tokens

tailwind-reviewer

Reviews code changes for correct Tailwind CSS v4 usage. Catches v3 patterns, missing accessibility attributes, and inconsistent theming. Use after generating or modifying Tailwind code.

RoninForge/roninforge-tailwind-v4 · 41 tokens

ijfw-accessibility-reviewer

Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.

FerroxLabs/ijfw · 37 tokens

ijfw-accessibility-eng

Audits frontend dashboard surfaces for WCAG AA conformance. Trigger after any dashboard UI change.

FerroxLabs/ijfw · 25 tokens

codedna-reviewer

CodeDNA compliance reviewer. Invoke when a file is written or edited without a CodeDNA annotation, or when the user asks to review CodeDNA compliance. Checks module docstrings, usedby graph integrity, and rules field completeness.

Larens94/codedna · 50 tokens

fec-performance-optimizer

Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…

bovinphang/frontend-craft · 0 tokens